Method, apparatus, and computer program product for determining play events and outputting events based on real-time data for proximity, movement of objects, and audio data

ABSTRACT

Systems, methods, apparatuses, and computer readable media are disclosed for determining events and outputting events based on real-time data for location and movement of objects and audio data. In one embodiment, a method is provided for a method of determining play events that at least includes receiving audio data, wherein the audio data is received from at least one of a memory or a sensor; determining an event probability based on comparing the audio data to an audio profile; and generating an event based on the event probability satisfying a predetermined threshold.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims priority from and the benefit of the filing date of U.S. Provisional Patent Application No. 61/831,990 filed Jun. 6, 2013, the contents of which is incorporated by reference in its entirety herein.

FIELD

Embodiments discussed herein are related to radio frequency locating and, more particularly, to systems, methods, apparatuses, computer readable media and other means for determining events.

BACKGROUND

Producing analysis of performance for sports events and/or teams is generally a resource intensive process often involving experienced individuals manually reviewing games or recordings of games to compile events and statistics for a game and the participants. Such analysis may be error prone as it requires reviewing a large number of participants moving among complex formations at each moment of a game. One of the subcategories of analysis is the determination of plays and the players involved in each.

A number of deficiencies and problems associated with providing performance analytics are identified herein. Through applied effort, ingenuity, and innovation, exemplary solutions to many of these identified problems are embodied by the present invention, which is described in detail below.

BRIEF SUMMARY

Systems, methods, apparatuses, and computer readable media are disclosed for providing real-time collection and analysis of participant (e.g., player) performance, events, and statistics during a sporting event or other group activity using a locating system, such as a radio frequency locating system, in conjunction with real time audio stream as herein described.

Embodiments of the present invention may provide for automatic recognition of formations, plays, and events during a sporting event through the processing of real time (or near real time) data regarding location, change in location, change in acceleration, orientation, audio data, sensor data, or the like, for participants that comprise a team or are otherwise associated with a sporting event or other group activity and how such data fits models that define the formations, plays, and events. Once such formations, plays, and events have been defined or identified they may be used to operate, control, or drive analytics or control systems such as, without limitation, visualization systems, game operations systems, camera control systems, team analytics systems, league analytics systems, statistics systems, and XML feed/IM feed systems.

In one embodiment, a method of determining events is provided, the method comprising receiving audio data, wherein the audio data is received from at least one of a memory or a sensor; determining an event probability based on comparing the audio data to an audio profile; and generating an event based on event probability satisfying a predetermined threshold.

In another embodiment, the method of determining events further comprises receiving a tag location data; determining an event probability based on comparing the tag location data to an event profile. In another embodiment, the method of determining events further comprises associating a time data with the audio data; and associating the time data with the location data. In another embodiment, the method of determining events further comprises synchronizing the audio data and location data based on the time data. In another embodiment, the method of determining events further comprises determining an event probability based on comparing audio data and location data to an event model.

In another embodiment, the method of determining events further comprises causing the event to be stored in a memory. In another embodiment, the method of determining events further comprises causing the event to be displayed on a user interface. In another embodiment, the method of determining events further comprises outputting the event to at least one of the group visualization system, a game operations system, a camera control system, a team analytics system, a league analytics system, a statistics system, an XML feed and/or instant message feed, and a historical data store/engine.

In some embodiments, an apparatus for determining play events is provided comprising at least one processor and at least one memory including computer instructions configured to, in cooperation with the at least one processor, cause the apparatus to receive audio data, wherein the audio data is received from at least one of a memory or a sensor; determine an event probability based on comparing the audio data to an audio profile; and generate an event based on event probability satisfying a predetermined threshold.

In another embodiment, the apparatus may further comprise the at least one processor and at least one memory including computer instructions configured to, in cooperation with the at least one processor cause the apparatus to receive a tag location data; and determine an event probability based on comparing the tag location to an event profile. In another embodiment, the apparatus may further comprise the at least one processor and at least one memory including the computer instructions configured to, associate a time data with the audio data; and associate the time data with the location data.

In another embodiment, the apparatus may further comprise the at least one processor and at least one memory including the computer instructions configured to, synchronize the audio data and location data based on the time data. In another embodiment, the apparatus may further comprise the at least one processor and at least one memory including the computer instructions configured to, determine an event probability based on comparing audio data and location data to an event model.

In another embodiment, the apparatus may further comprise the at least one processor and at least one memory including the computer instructions configured to, cause the event to be stored in a memory. In another embodiment, the apparatus may further comprise the at least one processor and at least one memory including the computer instructions configured to, cause the event to be displayed on a user interface.

In another embodiment, the apparatus may further comprise the at least one processor and at least one memory including the computer instructions configured to, output the event to at least one of the group visualization system, a game operations system, a camera control system, a team analytics system, a league analytics system, a statistics system, an XML feed and/or instant message feed, and a historical data store/engine.

In some embodiments, a computer program product for monitoring participants is provided, the computer program product comprising a non-transitory computer readable storage medium and computer program instructions stored therein, the computer program instructions comprising program instructions at least configured to receive audio data, wherein the audio data is received from at least one of a memory or a sensor; determine an event probability based on comparing the audio data to an audio profile; and generate an event based on event probability satisfying a predetermined threshold.

In another embodiment, the computer program product may further comprises computer program instructions at least configured to receive a tag location data; determine an event probability based on comparing the tag location data to an event profile. In another embodiment, the computer program product may further comprises computer program instructions at least configured to associate a time data with the audio data; and associate the time data with the location data.

In another embodiment, the computer program product may further comprises computer program instructions at least configured to synchronize the audio data and location data based on the time data. In another embodiment, the computer program product may further comprises computer program instructions at least configured to determine an event probability based on comparing audio data and location data to an event model.

In another embodiment, the computer program product may further comprises computer program instructions at least configured to cause the event to be stored in a memory. In another embodiment, the computer program product may further comprises computer program instructions at least configured to cause the event to be displayed on a user interface.

In another embodiment, the computer program product may further comprises computer program instructions at least configured to output the event to at least one of the group visualization system, a game operations system, a camera control system, a team analytics system, a league analytics system, a statistics system, an XML feed and/or instant message feed, and a historical data store/engine.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING(S)

Having thus described the invention in general terms, reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:

FIG. 1 illustrates an exemplary environment using a radio frequency locating system and audio sensors for determining an event in accordance with some embodiments of the present invention;

FIGS. 2A-C illustrate some exemplary participants carrying tags and audio sensors that may provide information for event determination in accordance with some embodiments of the present invention;

FIGS. 3A-3E are block diagrams showing the input and output of receivers and sensor receivers in accordance with an example embodiment;

FIG. 4 illustrates an exemplary system for providing event data in accordance with some embodiments of the present invention;

FIG. 5 illustrates example participant tracking over time in accordance with some embodiments of the present invention;

FIG. 6 illustrates a flowchart of an exemplary process for determining an event based on audio data and/or location data in accordance with some embodiments of the present invention; and

FIG. 7 illustrates a block diagram of components that may be included in an apparatus that may determine event data in accordance with some of the embodiments of the present invention.

DETAILED DESCRIPTION

The present invention now will be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all embodiments of the inventions are shown. Indeed, the invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. Like numbers refer to like elements throughout.

Overview

Existing performance analytics of sporting events have drawbacks in providing accurate data about events and participant actions that occur during a game. Game day data is often manually collected by individuals documenting play events, e.g., participant actions and play participation during a game. Performance review of a game often requires individuals to manually review game recordings over a number of hours after a game to compile player actions and events during play. This performance review is also often limited to statistics and data that can be identified or captured by the individuals watching or reviewing a game or game film. In addition, such performance reviews and any analytics data flowing therefrom are provided freely on a non-exclusive basis as anyone with access to game film can compile similar analytics data.

Embodiments of the present invention are directed to methods, systems, apparatuses, and computer readable storage media for providing real-time collection of data and analysis of participant performance and play statistics during a game such as by using radio frequency locating systems and radio frequency identification (“RFID”) in conjunction with audio data.

Embodiments of the present invention may provide for automatic recognition of formations, plays, and events through the processing of real time data (or near real time data) regarding location, change in location, velocity, change in acceleration, orientation, or the like, for participants based on an analysis of relevant models and data as described in detail below. The term “participant” as used herein refers to players, officials, game related objects such as the ball, penalty markers, line of scrimmage and yard to gain markers, and any other movable object proximate a field of play.

In embodiments where participants are players, a group or plurality of participants may be grouped into squads (e.g., offense, defense, kickoff, punt, kick return, punt return, field goal, infield, outfield, bullpen, etc.) and/or teams (e.g., football team, baseball team, swim team, etc.). Participants on the same team are called team mates; participants on different teams are called adversaries.

Embodiments of the present invention may provide for automated data collection with reduced errors, as well as providing additional statistics that may not be available with current systems. Additionally, embodiments may provide for rapid (i.e., near instantaneous) production of game review documentation (e.g., playbooks). Embodiments of the present invention may also provide additional and exclusive data and analysis that may be securely licensed without concern that similar analytics may be readily reproduced without a system configured as set forth below.

Embodiments of the present invention may allow for the simultaneous tracking of a plurality of participants and may provide for indications of player statistics and/or potential play events in real time (or near real time). Such indications may be output to a variety of systems including, without limitation, a visualization system (e.g., an enhanced television broadcast system or computer graphics visualization system), a game operations system, a camera control system, a team analytics system, a league analytics system, and a statistics system.

Embodiments of the present invention are illustrated in the appended figures and description below in relation to the sport of American football. However, as will be apparent to one of ordinary skill in the art in view of this disclosure, the inventive concepts herein described are not limited to football and may be applied to various other applications including, without limitation, other sports or group events such as baseball, basketball, golf, hockey, soccer, racing or motorsports, competitive events, and the like.

Example RF Locating System Architecture

FIG. 1 illustrates a radio frequency locating system useful for determining the location of an object (e.g. a football player on a football field) by determining RF location tag 102 (e.g., a ultra-wide band (UWB) location tag) location information at each receiver 106 (e.g., UWB reader, etc.); a timing reference clock to synchronize the frequency of counters within each receiver 106; and, in some examples, a reference tag 104, preferably a UWB transmitter, positioned at known coordinates to enable phase offset between counters to be determined. The systems described herein may be referred to as either “multilateration” or “geolocation” systems; terms which refer to the process of locating a signal source by solving for the mathematical intersection of multiple hyperbolae determined by the difference of arrival times of a signal received at multiple receivers.

In some examples, the system comprising at least the tags 102 and the receivers 106 is configured to provide two dimensional and/or three dimensional precision localization (e.g., subfoot resolutions), even in the presence of multipath interference, due in part to the use of short nanosecond duration pulses whose time-of-flight can be accurately determined using detection circuitry, such as in the receivers 106, which can trigger on the leading edge of a received waveform. In some examples, this short pulse characteristic allows necessary data to be conveyed by the system at a higher peak power, but lower overall power levels, than a wireless system configured for high data rate communications, yet still operate within local regulatory requirements which may limit overall power levels.

In some examples, the tags 102 may operate with an instantaneous −3 dB bandwidth of approximately 400 MHz and an average transmission rate below a 187.5 kHz regulatory cutoff. In such examples, the predicted maximum range of the system, operating at 6.0 GHz, is roughly 311 meters. Such a configuration advantageously satisfies constraints applied by regulatory bodies related to peak and average power densities (e.g., effective isotropic radiated power density), while still optimizing system performance related to range and interference. In further examples, tag transmissions with a −3 dB bandwidth of approximately 400 MHz yields, in some examples, an instantaneous pulsewidth of roughly 2.5 nanoseconds which enables a resolution to better than 30 centimeters.

Referring again to FIG. 1, the object to be located has an attached RF location tag 102, preferably a tag having a UWB transmitter, that transmits a signal comprising a burst (e.g., 72 pulses at a burst rate of 1 Mb/s), and optionally, a burst having a tag data packet that may include tag data elements that may include, but are not limited to, a tag unique identification number (tag UID), other identification information, a sequential burst count, stored tag data, or other desired information for object or personnel identification, inventory control, etc. In some embodiments, the tag data packet may include a tag-individual correlator that can be used to associate a specific individual (e.g., participant) with a specific tag. In some examples, the sequential burst count (e.g., a packet sequence number) from each tag 102 may be advantageously provided in order to permit, at a receiver hub 108, correlation of time of arrival (TOA) measurement data from various receivers 106.

In some examples, the RF location tag 102 may employ UWB waveforms (e.g., low data rate waveforms) to achieve extremely fine resolution because of their extremely short pulse (i.e., sub-nanosecond to nanosecond, such as a 2 ns (ins up and Ins down)) durations. As such, the tag data packet may be of a short length (e.g., 72-112 bits in some example embodiments), that advantageously enables a higher throughput and higher transmission rates. In some examples, higher throughput and/or higher transmission rates may result in larger datasets for filtering to achieve a more accurate location estimate. In some examples, rates of up to approximately 2600 updates per second can be accommodated without exceeding regulatory requirements. Alternatively or additionally, in some examples, the length of the tag data packets, in conjunction with other system functionality, may also result in a longer battery life (e.g., a 3.0 v 1 A-hr lithium cell battery may result in a tag battery life in excess of 3.8 years).

In some examples, one or more other tags, such as a reference tag 104, may be positioned within and/or about a monitored area or zone, such as monitored area 100 illustrated herein as a football field. In some examples, the reference tag 104 may be configured to transmit a signal that is used to measure the relative phase (e.g., the count of free-running counters) of non-resettable counters within the receivers 106.

One or more (preferably four or more) receivers 106 are also at locations with predetermined coordinates within and/or around the monitored area 100. In some examples, the receivers 106 may be connected in a “daisy chain” fashion to advantageously allow for a large number of receivers 106 to be interconnected over a significant monitored area in order to reduce and simplify cabling, reduce latency, provide power and/or the like. Each of the receivers 106 includes a receiver for receiving transmissions, such as UWB transmissions, and preferably, a packet decoding circuit that extracts a time of arrival (TOA) timing pulse train, transmitter ID, packet number and/or other information that may have been encoded in the tag transmission signal (e.g., material description, personal information, etc.) and is configured to sense signals transmitted by the tags 102 and one or more reference tags 104 (if present).

Each receiver 106 includes a time measuring circuit that measures time differences of arrival (TDOA) of tag bursts. The time measuring circuit is phase-locked (e.g., phase differences do not change and therefore respective frequencies are identical) with a common digital reference clock signal distributed via cable connection from a receiver hub 108 having a central timing reference clock generator. The reference clock signal establishes a common timing reference for the receivers 106. Thus, multiple time measuring circuits of the respective receivers 106 are synchronized in frequency, but not necessarily in phase. While there typically may be a phase offset between any given pair of receivers in the receivers 106, the offset is readily determined through use of a reference tag 104. Alternatively or additionally, each receiver may be synchronized wirelessly via virtual synchronization without a dedicated physical timing channel.

In some example embodiments, the receivers 106 are configured to determine various attributes of the received signal. Since measurements are determined at each receiver 106, in a digital format, rather than analog, signals are transmittable to the receiver hub 108. Advantageously, because packet data and measurement results can be transferred at high speeds to a receiver memory, the receivers 106 can receive and process tag (and corresponding object) locating signals on a nearly continuous basis. As such, in some examples, the receiver memory allows for a high burst rate of tag events (i.e., tag data packets) to be captured.

Data cables or wireless transmissions may convey measurement data from the receivers 106 to the receiver hub 108 (e.g., the data cables may enable a transfer speed of 2 Mbps). In some examples, measurement data is transferred to the receiver hub at regular polling intervals.

As such, the receiver hub 108 determines or computes tag location (i.e., object location) by processing TDOA measurements related to multiple data packets detected by the receivers 106. In some example embodiments, the receiver hub 108 may be configured to resolve the coordinates of a tag using nonlinear optimization techniques. The receiver hub 108 may also be referred to herein as a locate engine or a receiver hub/locate engine.

In some examples, the system described herein may be referred to as an “over-specified” or “over-determined” system. As such, the receiver hub 108 may then calculate one or more valid (i.e., most likely) locations based on a set of measurements and/or one or more incorrect (i.e., less likely) locations. For example, a location may be calculated that is impossible due the laws of physics (e.g., a tag on a football player that travels more than 100 yards in 1 second) or may be an outlier when compared to other locations. As such one or more algorithms or heuristics may be applied to minimize such error.

One such algorithm for error minimization, which may be referred to as a time error minimization algorithm, may be described as:

$ɛ = {\sum\limits_{j = 1}^{N}{\sum\limits_{k = {j + 1}}^{N}\left\{ {\left( {t_{j} - t_{k}} \right) - {\frac{1}{c}\begin{bmatrix} {\left\lbrack {\left( {x - x_{j}} \right)^{2} + {\left( {y - y_{j}} \right)^{2}\left( {z - z_{j}} \right)^{2}}} \right\rbrack^{\frac{1}{2}} -} \\ \left\lbrack {\left( {x - x_{k}} \right)^{2} + \left( {y - y_{k}} \right)^{2} + \left( {z - z_{k}} \right)^{2}} \right\rbrack^{\frac{1}{2}} \end{bmatrix}}} \right\}^{2}}}$

where N is the number of receivers, c is the speed of light, x_(j,k), y_(j,k) and z_(j,k) are the coordinates of the receivers and t_(j,k) are the arrival times received at each of the receivers. Note that only time differences may be evaluated at hub 108 in some example embodiments. The starting point for the minimization may be obtained by first doing an area search on a coarse grid of x, y and z over an area defined by the user and followed by a localized steepest descent search.

Another or second algorithm for error minimization, which may be referred to as a distance error minimization algorithm, may be defined by:

$ɛ = {\sum\limits_{j = 1}^{N}\left\lbrack {\left\lbrack {\left( {x - x_{j}} \right)^{2} + \left( {y - y_{j}} \right)^{2} + \left( {z - z_{j}} \right)^{2}} \right\rbrack^{\frac{1}{2}} - {c\left( {t_{j} - t_{0}} \right)}} \right\rbrack^{2}}$

where time and location differences are replaced by their non-differential values by incorporating an additional unknown dummy variable, t₀, which represents an absolute time epoch. The starting point for this algorithm is fixed at the geometric mean position of all active receivers. No initial area search is needed, and optimization proceeds through the use of a DavidonFletcher-Powell (DFP) quasi-Newton algorithm in some examples. In other examples, a steepest descent algorithm may be used.

In order to determine the coordinates of a tag (T), in some examples and for calibration purposes, a reference tag (e.g., reference tag 104) is positioned at a known coordinate position (x_(T), y_(T), z_(T)).

In further example embodiments, a number N of receivers {R_(j): j=1, . . . , N} (e.g., receivers 106) are positioned at known coordinates (x_(R) _(j) , y_(R) _(j) , z_(R) _(j) ), which are respectively located at distances, such as:

d _(Rj)=√{square root over ((x _(Rj) −x _(T))²+(y _(Rj) −y _(T))²+(z _(Rj) −z _(T))²)}{square root over ((x _(Rj) −x _(T))²+(y _(Rj) −y _(T))²+(z _(Rj) −z _(T))²)}{square root over ((x _(Rj) −x _(T))²+(y _(Rj) −y _(T))²+(z _(Rj) −z _(T))²)}

from a reference tag.

Each receiver R_(j) utilizes, for example, a synchronous clock signal derived from a common frequency time base, such as clock generator. Because the receivers are not synchronously reset, an unknown, but constant offset O_(j) exists for each receiver's internal free running counter. The value of the offset O_(j) is measured in terms of the number of fine resolution count increments (e.g., a number of nanoseconds for a one nanosecond resolution system).

The reference tag is used to calibrate the radio frequency locating system as follows:

The reference tag emits a signal burst at an unknown time τ_(R). Upon receiving the signal burst from the reference tag, a count N_(R) _(j) as measured at receiver R_(j) is given by

N _(R) _(j) =βτ_(R) +O _(j) +βd _(R) _(j) /c

where c is the speed of light and β is the number of fine resolution count increments per unit time (e.g., one per nanosecond). Similarly, each object tag T_(i) of each object to be located transmits a signal at an unknown time τ_(i) to produce a count

N _(i) _(j) =βτ_(i) +O _(j) +βd _(i) _(j) /c

at receiver R_(j) where d_(i) _(j) is the distance between the object tag T_(i) and the receiver at receiver R_(j). Note that τ_(i) is unknown, but has the same constant value for receivers of all receivers R_(j). Based on the equalities expressed above for receivers R_(j) and R_(k) and given the reference tag information, differential offsets expressed as differential count values are determined as follows:

${N_{R_{j}} - N_{R_{k}}} = {\left( {O_{j} - O_{k}} \right) + {\beta\left( {\frac{d_{R_{j}}}{c} - \frac{d_{R_{k}}}{c}} \right)}}$ or $\begin{matrix} {\left( {O_{j} - O_{k}} \right) = {\left( {N_{R_{j}} - N_{R_{k}}} \right) - {\beta\left( {\frac{d_{R_{j}}}{c} - \frac{d_{R_{k}}}{c}} \right)}}} \\ {= \Delta_{j_{k}}} \end{matrix}$

Δ_(jk) is constant as long as d_(Rj)−d_(Rk) remains constant, (which means the receivers and tag are fixed and there is no multipath situation) and β is the same for each receiver. Note that Δ_(j) _(k) is a known quantity, since N_(R) _(j) , N_(R) _(k) , β, d_(R) _(j) /c, and d_(R) _(k) /c are known. That is, the differential offsets between receivers R_(j) and R_(k) may be readily determined based on the reference tag transmissions. Thus, again from the above equations, for an object tag (T_(i)) transmission arriving at receivers R_(j) and R_(k):

N _(i) _(j) −N _(i) _(k) =(O _(j) −O _(k))+β(d _(i) _(j) /c−d _(i) _(k) /c)=Δ_(j) _(k) +β(d _(i) _(j) /c−d _(i) _(k) /c)

or,

d _(i) _(j) −d _(i) _(k) =(c/β)[N _(i) _(j) −N _(i) _(k) −Δ_(j) _(k) ],

The process further includes determining a minimum error value for each object tag T_(i), according to the functional relationship:

$E_{i} = {\min\limits_{({x,y,z})}{\sum\limits_{j}^{\;}{\sum\limits_{k > j}^{\;}\left\lbrack {\left( {d_{i_{j}} - d_{i_{k}}} \right) - \left( {{{dist}\left( {T_{x,y,z},R_{j}} \right)} - {{dist}\left( {T_{x,y,z},R_{k}} \right)}} \right)} \right\rbrack^{2}}}}$ where ${{dist}\left( {T_{x,y,z},R_{j}} \right)} = \sqrt{\left( {x_{R_{j}} - x} \right)^{2} + \left( {y_{R_{j}} - y} \right)^{2} + \left( {z_{R_{j}} - z} \right)^{2}}$

is the Euclidean distance between point (x,y,z) and the coordinates of the j^(th) receiver R_(j). The minimization solution (x′,y′,z′) is the estimated coordinate location for the i^(th) tag at t₀.

In an example algorithm, this proceeds according to:

$ɛ = {\sum\limits_{j = 1}^{N}\left\lbrack {\left\lbrack {\left( {x - x_{j}} \right)^{2} + \left( {y - y_{j}} \right)^{2} + \left( {z - z_{j}} \right)^{2}} \right\rbrack^{\frac{1}{2}} - {c\left( {t_{j} - t_{0}} \right)}} \right\rbrack^{2}}$

where each arrival time, t_(j), is referenced to a particular receiver (receiver “1”) as follows:

$t_{j} = {\frac{1}{\beta}\left( {N_{j} - N_{1} - \Delta_{j_{k}}} \right)}$

and the minimization is performed over variables (x, y, z, t₀) to reach a solution (x′, y′, z′, t₀′).

In some example embodiments, the location of a tag 102 may then be output to a receiver processing and distribution system 110 for further processing of the location data to advantageously provide visualizations, predictive analytics, statistics and/or the like.

The exemplary radio frequency locating system of FIG. 1 may be used in providing performance analytics in accordance with some embodiments of the present invention. In the environment of FIG. 1, data may be captured and analyzed, such as during a sporting event to identify events, statistics, and other data useful to a sports team, league, viewer, licensee, or the like. In some embodiments, data associated with a number of objects or participants (e.g., players, officials, balls, game equipment, etc.) on a playing field, such as monitored area 100, may be generated and provided to a performance analytics system. As such, as further discussed in connection with FIGS. 2A-C below, each object may have one or more attached tags 102 (such as to equipment worn by a player) to be used to track data such as location, change of location, speed, or the like of each object. In some embodiments, additional sensors, such as, without limitation, accelerometers, magnetometers, time-of-flight sensors, health sensors, temperature sensors, moisture sensors, light sensors, or the like, may be attached to each object to provide further data to the performance analytics system. Such additional sensors may provide data to the tag 102, either through a wired or wireless connection, to be transmitted to the receivers 106 or the sensors may be configured to transmit data to receivers (i.e., sensor receivers) separately from tags 102.

One or more of the receivers 106 may receive transmissions from tags 102 and transmit the blink data to a receiver hub 108. The receiver hub 108 may process the received data to determine tag location for the tags 102. The receiver hub 108 may transmit the tag location data to one or more processors, such as receiver processing and distribution system 110. Receiver processing and distribution system 110 may use one or more modules (e.g., processing engines) and one or more databases to identify the object each of the tags 102 is associated with, such as a player, official, ball, or the like.

In some embodiments, multiple tags 102 (as well as other sensors) may be attached to the equipment worn by an individual player, official, or other participant. The receiver processing and distribution system 110 may use one or more databases to associate the tag identifier (e.g., a tag UID) of each tag 102 with each player, official, object, or other participant and correlate the tag location data and/or other tag and sensor derived data for multiple tags 102 that are associated with a particular player, official, object, or other participant.

In some embodiments, audio sensors 105 are placed on participants and in fixed locations around the monitored area 100. Audio sensors 105 may also be moved throughout the monitored area (usually associated with a tag to determine location) or aimed by nonparticipant personnel. An “audio sensor” is simply one type of “sensor” (e.g., sensor 203 discussed below) that is discussed separately in order to illustrate the generation and use of audio data in accordance with various embodiments. Audio sensors may comprise, without limitation, shotgun microphones, parabolic microphones, directional microphones, participant mounted microphones (e.g., helmet, wristbands, shoulder pads, apparel, etc.), piezoelectric sound sensors, personnel microphones (e.g., mounted to the body of the participant rather than to apparel), official call microphones, and the like. Audio sensors 105 are configured to generate audio data as defined below.

In one embodiment, audio sensors 105 may be configured to provide audio data to the tag 102, either through a wired or a wireless connection, to be transmitted to the receivers 106 as discussed in greater detail below. In another embodiment, audio sensors 105 may be configured to transmit data to receivers 106 and/or sensor receivers 166 (shown in FIG. 3B) separately from tags 102.

As discussed in greater detail below, the receiver processing and distribution system 110 may then use the tag location data and/or other tag, sensor derived data (including audio data) to determine player and play dynamics, such as a player's location, how the location is changing with time, orientation, velocity, acceleration, deceleration, total yardage, or the like. The receiver processing and distribution system 110 may also use the tag location data and/or other tag and sensor derived data to determine dynamics for other participants such as the officials, the ball, penalty markers, line of scrimmage or yards to gain markers, or the like, for use in generating data for performance analytics. The receiver processing and distribution system 110 may also use the data and one or more databases to determine team formations, play activity, events, statistics, or the like, such as by comparing the data to various models to determine the most likely formation or play or the events that have occurred during a game. The receiver processing and distribution system 110 may also use the data to provide statistics or other output data for the players, teams, and the game.

As will be apparent to one of ordinary skill in the art, the inventive concepts herein described are not limited to use with the UWB based RF locating system shown in FIG. 1. Rather, in various embodiments, the inventive concepts herein described may be applied to various other locating systems especially those that are configured to provide robust location resolution (i.e., subfoot location resolution).

Example Tag/Sensor Positioning and Participant Correlation

FIG. 1 shows a monitored area 100. The monitored area 100 comprises a plurality of positions at one or more time epochs. The plurality of positions may be divided into one or more regions, called zones. Each zone may be described by one or more coordinate systems, such as a local NED (North-East-Down) system, a latitude-longitude system, or even a yard line system as might be used for an American football game. A location is a description of a position, or a plurality of positions, within the monitored area. For example, a field marker at the intersection of the south goal line and west out of bounds line at Bank of America Stadium in Charlotte, N.C. could be described as {0,0,0} in a local NED system, or 35.225336 N 80.85273 W longitude 751 ft. altitude on a latitude-longitude system, or simply “Panthers Goal Line” in a yard line system. Because different types of locating systems or different zones within a single locating system may use different coordinate systems, a Geographical Information System or similar monitored area database may be used to associate location data. One type of Geographical Information System describing at least a field of play may be called Field Data.

FIGS. 2A-C illustrate some exemplary participants that may provide information to a performance analytics system in accordance with some embodiments of the present invention. FIG. 2A illustrates a player 202 (e.g., a football player) wearing equipment having attached tags 102 in accordance with some embodiments. In particular, the depicted player 202 is wearing shoulder pads having tags 102 affixed to opposite sides thereof. This positioning advantageously provides an elevated broadcast position for each tag 102 thereby increasing its communication effectiveness.

Additional sensors 203 may be attached to equipment worn by player 202, such as accelerometers, magnetometers, time-of-flight sensors, health monitoring sensors (e.g., blood pressure sensors, heart monitors, respiration sensors, moisture sensors, temperature sensors), light sensors, audio sensors, or the like. The additional sensors 203 may be affixed to shoulder pads, the helmet, the shoes, rib pads, elbow pads, the jersey, the pants, a bodysuit undergarment, gloves, arm bands, wristbands, and the like.

FIG. 2A depicts audio sensors 105 mounted to the player 202 separately from the 203 for illustration purposes. However, as was discussed above, an audio sensor 105 is simply one type of sensor 203. The depicted audio sensors 105 are attached to equipment worn by the player 202 and may include a piezoelectric sound sensor or microphone. In some embodiments, the audio sensors 105 may be affixed to the helmet, shoulder pads, jersey, and any other position on the player that is described herein as receiving a sensor.

As discussed in further detail below, the positioning of audio sensors 105 on the helmet or jersey of the player may allow the receiver processing and distributing system 110 to determine particular sounds (i.e., audio data) produced by or near the player (Quarterback cadence, field directions, impact noise, snap, or the like).

Sensors 203 (including audio sensors 105) may be configured to communicate with receivers (e.g., receivers 106 of FIG. 1) directly or indirectly through tags 102 or other transmitters. For example, in one embodiment, a sensor 203 may be connected, wired (e.g., perhaps through wires sewn into a jersey or bodysuit undergarment) or wirelessly, to tags 102 to provide sensor data (including, for example, audio data) to tags 102, which is then transmitted to the receivers 106. In another embodiment, a plurality of sensors (not shown) may be connected to a dedicated antenna or transmitter, perhaps positioned in the helmet, which may transmit sensor data to one or more receivers.

FIG. 2B illustrates a game official 206 wearing equipment having attached tags 102, sensors 203, and audio sensors 105 in accordance with some embodiments. In the depicted embodiment, tags 102 are attached to the official's jersey 209 proximate opposite shoulders. Sensors 203 (e.g., accelerometers) are positioned in wristbands worn on the official's wrists as shown. Audio sensors 105 are positioned on, affixed to, or embedded within the official whistle 207 and affixed to the official's jersey 209. Sensors 203 (including the audio sensors 105) may be configured to communicate with receivers (e.g., receivers 106 of FIG. 1) directly or indirectly through tags 102 or other transmitters as discussed above in connection with FIG. 2A.

As discussed in greater detail below, the positioning of sensors 203 (here, accelerometers) proximate the wrists of the official may allow the receiver processing and distribution system 110 to determine particular motions, movements, or activities of the official 206 for use in determining events (e.g., winding of the game clock, first down, touchdown, or the like). The official 206 may also carry other equipment, such as penalty flag 208, which may also have a tag 102 (and optionally one or more sensors) attached to provide additional data to the receiver processing and distribution system 110. For example, the receiver processing and distribution system 110 may use tag location data from the penalty flag 208 to determine when the official is merely carrying the penalty flag 208 versus when the official is using the penalty flag 208 to indicate an event, such as a penalty (e.g., by throwing the penalty flag 208).

As discussed in further detail below, the positioning of audio sensors 105 proximate the official whistle 207 and jersey 209 may allow the receiver processing and distributing system 110 to determine particular sounds (e.g., audio data) produced by or near the official (whistle sounds, official calls, player sounds, inter-official communication, or the like).

FIG. 2C illustrates an example of a ball 210 having tags 102 attached or embedded in accordance with some embodiments. Additionally, sensors 203 may be attached to or embedded in the ball 210, such as accelerometers, time-of-flight sensors, audio sensors, or the like. In some embodiments, the sensor 203 may be connected, wired or wirelessly, to tag 102 to provide sensor data to tag 102 which is then transmitted to the receivers 106. In some embodiments, the sensor 203 may transmit sensor data to receivers separately from the tag 102, such as described above in connection with FIG. 2A.

As will be apparent to one of ordinary skill in the art in view of this disclosure, once the tags 102, sensors 203, and audio sensors 105 of FIGS. 2A-C are positioned on participants, they may be correlated to such participants. For example, in some embodiments, unique tag or sensor identifiers (“unique IDs”) may be correlated to a participant profile (e.g., John Smith —running back, Fred Johnson—line judge official, or ID 027—one of several game balls, etc.) and stored to a remote database accessible to the performance analytics system as discussed in greater detail below. Each participant profile may further include or be correlated with a variety of data including, but not limited to, biometric data (e.g., height, weight, health data, etc.), role data, team ID, performance statistics, and other data that may be apparent to one of skill in the art in view of the foregoing description.

In some embodiments, such participant profile or role data may be pre-defined and stored in association with the unique tag or sensor identifiers. In other embodiments, the participant profile or role data may also be “learned” by the system as a result of received tag or sensor data, formation data, play data, event data, and/or the like. For example, in some embodiments the system may determine that a tag or sensor is not correlated to a participant profile and may analyze data received from the tag and/or sensor to determine possible participant roles, etc., which may be ranked and then selected/confirmed by the system or by a user after being displayed by the system. In some embodiments, the system may determine possible participant roles (i.e., participant role data) based on determined participant location data (e.g., movement patterns, alignment position, etc.).

In some embodiments, as described in greater detail below, the participant profile or role data may also be updated by the system (i.e., to produce a data set for the participant that is far more robust than that established at initial registration) as a result of received tag or sensor data, formation data, play data, event data, and/or the like. In some embodiments, the participant profile and/or role data may be used in a performance analytics system to weight the actions of the participants during analysis to assist in qualifying what is occurring, such as in determining formations, plays, events, etc.

Tag ID and Sensor Data Transmission Architecture

FIGS. 3A, 3B, 3C, 3D, and 3E show block diagrams of various different architectures that may be utilized in transmitting signals from one or more tags and sensors to one or more receivers of a receiver processing and analytics system in accordance with embodiments of the invention. In some embodiments, the depicted architectures may be used in connection with the receiver processing and analytics system 110 of FIG. 1. More than one of these architectures may be used together in a single system.

FIG. 3A shows a RF location tag 102, such as that shown in FIG. 1, which may be configured to transmit a tag signal to one or more receivers 106. The one or more receivers 106 may transmit a receiver signal to the receiver hub/locate engine 108.

The depicted RF location tag 102 may generate or store a tag unique identifier (“tag UID”) and/or tag data as shown. The tag data may include useful information such as the installed firmware version, last tag maintenance date, configuration information, and/or a tag-individual correlator. The tag-individual correlator may comprise data that indicates that a monitored individual (e.g., participant) is associated with the RF location tag 102 (e.g., name, uniform number and team, biometric data, tag position on individual, i.e., right wrist). As will be apparent to one of skill in the art in view of this disclosure, the tag-individual correlator may be stored to the RF location tag 102 when the tag is registered or otherwise associated with an individual. While shown as a separate field for illustration purposes, one of ordinary skill in the art may readily appreciate that the tag-individual correlator may be part of any tag data or even omitted from the tag.

The tag signal transmitted from RF location tag 102 to receiver 106 may include “blink data” as it is transmitted at selected intervals. This “blink rate” may be set by the tag designer or the system designer to meet application requirements. In some embodiments, it is consistent for one or all tags; in some embodiments it may be data dependent. Blink data includes characteristics of the tag signal that allow the tag signal to be recognized by the receiver 106 so the location of the RF location tag 102 may be determined by the locating system. Blink data may also comprise one or more tag data packets. Such tag data packets may include any data from the tag 102 that is intended for transmission such as, for example in the depicted embodiment, a tag UID, tag data, and a tag-individual correlator. In the case of TDOA systems, the blink data may be or include a specific pattern, code, or trigger that the receiver 106 (or downstream receiver processing and analytics system) detects to identify that the transmission is from a RF location tag 102 (e.g., a UWB tag).

The depicted receiver 106 receives the tag signal, which includes blink data and tag data packets as discussed above. In one embodiment, the receiver 106 may pass the received tag signal directly to the receive hub/locate engine 108 as part of its receiver signal. In another embodiment, the receiver 106 could perform some basic processing on the received tag signal. For instance, the receiver could extract blink data from the tag signal and transmit the blink data to the receive hub/locate engine 108. The receiver could transmit a time measurement to the receive hub/locate engine 108 such as a TOA measurement and/or a TDOA measurement. The time measurement could be based on a clock time generated or calculated in the receiver, it could be based on a receiver offset value as explained at paragraph [0053] above, it could be based on a system time, and/or it could be based on the time difference of arrival between the tag signal of the RF location tag 102 and the tag signal of a RF reference tag (e.g., tag 104 of FIG. 1). The receiver 106 could additionally or alternatively determine a signal measurement from the tag signal (such as a received signal strength indication (RSSI), a direction of signal, signal polarity, or signal phase) and transmit the signal measurement to the receive hub/locate engine 108.

FIG. 3B shows a RF location tag 202 and sensor 203, such as those worn on an individual's person as shown in FIG. 2, which may be configured to transmit tag signals and sensor signals, respectively, to one or more receivers 106, 166. While the foregoing description refers only to a sensor 203 for illustration and brevity purposes, it is noted that the depicted sensor 203 may be an audio sensor 105. Said differently, the communication channels and procedures discussed in connection with FIGS. 3A-3E are as applicable to audio sensors 105 (one example type of sensor) as they are to sensors 203. The one or more receivers 106, 166 may then transmit receiver signals to the receiver hub/locate engine 108. One or more receivers 106, 166 may share physical components, such as a housing or antenna.

The depicted RF location tag 202 may comprise a tag UID and tag data (such as a tag-individual correlator) and transmit a tag signal comprising blink data as discussed in connection with FIG. 3A above. The depicted sensor 203 may generate and/or store a sensor UID, additional stored sensor data (e.g. a sensor-individual correlator, sensor type, sensor firmware version, last maintenance date, the units in which environmental measurements are transmitted, etc.), and environmental measurements (e.g., audio data). The “additional stored sensor data” of the sensor 203 may include any data that is intended for transmission to a RF location tag 202, a reference tag (e.g., 104 of FIG. 1), a sensor receiver, a receiver 106, and/or the receiver/hub locate engine 108.

The sensor-individual correlator may comprise data that indicates that a monitored individual is associated with the sensor 203 (e.g., name, uniform number and team, biometric data, sensor position on individual, i.e., right wrist). As will be apparent to one of skill in the art in view of this disclosure, the sensor-individual correlator may be stored to the sensor 203 when the sensor is registered or otherwise associated with an individual. While shown as a separate field for illustration purposes, one of ordinary skill in the art may readily appreciate that the sensor-individual correlator may be part of any additional stored sensor data or omitted from the sensor altogether.

Sensors such as sensor 203 that are structured according to embodiments of the invention may sense or determine one or more environmental conditions (e.g. temperature, pressure, pulse, heartbeat, audio data, rotation, velocity, acceleration, radiation, position, chemical concentration, voltage) and store or transmit “environmental measurements” that are indicative of such conditions. To clarify, the term “environmental measurements” includes measurements concerning the environment proximate the sensor including, without limitation, ambient information (e.g., temperature, position, humidity, sound, etc.) and information concerning an individual's health, fitness, operation, and/or performance. Environmental measurements may be stored or transmitted in either analog or digital form and may be transmitted as individual measurements, as a set of individual measurements, and/or as summary statistics. For example, temperature in degrees Celsius may be transmitted as {31}, or as {33, 32, 27, 22, 20, 23, 27, 30, 34, 31}, or as {27.9}. In some embodiments, the sensor-individual correlator could be determined at least in part from the environmental measurements.

In the depicted embodiment, RF location tag 202 transmits a tag signal to receiver 106 and sensor 203 transmits a sensor signal to sensor receiver 166. The sensor signal may comprise one or more sensor information packets. Such sensor information packets may include any data or information from the sensor 203 that is intended for transmission such as, for example in the depicted embodiment, sensor UID, additional stored sensor data, sensor-individual correlator, and environmental measurements. A receiver signal from receiver 106 and a sensor receiver signal from sensor receiver 166 may be transmitted via wired or wireless communication to receiver hub/locate engine 108 as shown.

FIG. 3C depicts a sensor 203 communicating through a RF location tag 202 in accordance with various embodiments. In one embodiment, the sensor 203 may be part of (i.e., reside in the same housing or assembly structure) of the RF location tag 202. In another embodiment, the sensor 203 may be distinct from (i.e., not resident in the same housing or assembly structure) the RF location tag 202 but configured to communicate wirelessly or via wired communication with the RF location tag 202.

In one embodiment, the RF location tag 202, the sensor 203, or both, may generate and/or store a tag-sensor correlator that indicates an association between a RF location tag 202 and a sensor 203 (e.g., tag UID/sensor UID, distance from tag to sensor in a particular stance, set of sensors associated with a set of tags, sensor types associated with a tag, etc.). In the depicted embodiment, both the RF location tag 202 and the sensor 203 store the tag-sensor correlator.

In the depicted embodiment, sensor 203 transmits a sensor signal to RF location tag 202. The sensor signal may comprise one or more sensor information packets as discussed above. The sensor information packets may comprise the sensor UID, a sensor-individual correlator, additional stored sensor data, the tag-sensor correlator, and/or the environmental measurements. The RF location tag 202 may store some portion of, or all of, the sensor information packets locally and may package the sensor information packets into one or more tag data packets for transmission to receiver 106 as part of a tag signal or simply pass them along as part of its tag signal.

FIG. 3D illustrates an example communication structure for a reference tag 104 (e.g., reference tag 104 of FIG. 1), an RF location tag 202, a sensor 203, and two receivers 106 in accordance with one embodiment. The depicted reference tag 104 is a RF location tag and thus may include tag data, a tag UID, and is capable of transmitting tag data packets. In some embodiments, the reference tag 104 may form part of a sensor and may thus be capable of transmitting sensor information packets.

The depicted sensor 203 transmits a sensor signal to RF reference tag 104. The RF reference tag 104 may store some portion or some or all of the sensor information packets locally and may package the sensor information packets into one or more tag data packets for transmission to receiver 106 as part of a tag signal, or simply pass them along as part of its tag signal.

As was described above in connection with FIG. 1, the receivers 106 of FIG. 3D are configured to receive tag signals from the RF location tag 202 and the reference tag 104. Each of these tag signals may include blink data, which may comprise tag UIDs, tag data packets, and/or sensor information packets. The receivers 106 each transmit receiver signals via wired or wireless communication to the receiver hub/locate engine 108 as shown.

FIG. 3E illustrates an example communication structure between an RF location tag 202, a plurality of receivers 106, and a variety of sensor types including, without limitation, a sensor 203 (e.g., an audio sensor 105), a diagnostic device 233, a triangulation positioner 243, a proximity positioner 253, and a proximity label 263 in accordance with various embodiments. In the depicted embodiment, none of the sensors 203, 233, 243, 253 form part of an RF location tag 202 or reference tag 104. However, each may comprise a sensor UID and additional stored sensor data. Each of the depicted sensors 203, 233, 243, 253 transmits sensor signals comprising sensor information packets.

In the depicted embodiment, receiver 106 is configured to receive a tag signal from RF location tag 202 and a sensor signal directly from sensor 203. In such embodiments, sensor 203 may be configured to communicate in a communication protocol that is common to RF location tag 202 as will be apparent to one of ordinary skill in the art in view of this disclosure.

FIG. 3E depicts one type of sensor referred to herein as a “proximity interrogator”. The proximity interrogator 223 can include circuitry operative to generate a magnetic, electromagnetic, or other field that is detectable by a RF location tag 202. While not shown in FIG. 3E, a proximity interrogator 223 may include a sensor UID and other tag and sensor derived data or information as discussed above.

In some embodiments, the proximity interrogator 223 is operative as a proximity communication device that can trigger a RF location tag 202 (e.g., when the RF location tag 202 detects the field produced by the proximity interrogator 223) to transmit blink data under an alternate blink pattern or blink rate. The RF location tag can initiate a preprogrammed (and typically faster) blink rate to allow more location points for tracking an individual. In some embodiments, the RF location tag may not transmit a tag signal until triggered by the proximity interrogator 223. In some embodiments the RF location tag 202 may be triggered when the RF location tag 202 moves near (e.g., within communication proximity to) a proximity interrogator 223. In some embodiments, the RF location tag may be triggered when the proximity interrogator 223 moves near to the RF location tag 202.

In other embodiments, the RF location tag 202 may be triggered when a button is pressed or a switch is activated on the proximity interrogator 223 or on the RF location tag itself. For example, a proximity interrogator 223 could be placed at the start line of a racetrack. Every time a car passes the start line, a car-mounted RF location tag 202 senses the signal from the proximity interrogator and is triggered to transmit a tag signal indicating that a lap has been completed. As another example, a proximity interrogator 223 could be placed at a Gatorade cooler. Each time a player or other participant fills a cup from the cooler a participant-mounted RF location tag 202 senses the signal from the proximity interrogator and is triggered to transmit a tag signal indicating that Gatorade has been consumed. As another example, a proximity interrogator 223 could be placed on a medical cart. When paramedics use the medical cart to pick up a participant (e.g., a player) and move him/her to the locker room, a participant-mounted RF location tag 202 senses the signal from the proximity interrogator and is triggered to transmit a tag signal indicating that they have been removed from the game. As explained, any of these post-triggered tag signals may differ from pre-triggered tag signals in terms of any aspect of the analog and/or digital attributes of the transmitted tag signal.

FIG. 3E depicts another type of sensor that is generally not worn by an individual but is referred to herein as a “diagnostic device”. However, like other sensors, diagnostic devices may measure one or more environmental conditions and store corresponding environmental measurements in analog or digital form.

While the depicted diagnostic device 233 is not worn by an individual, it may generate and store a sensor-individual correlator for association with environmental measurements taken in connection with a specific individual. For example, in one embodiment, the diagnostic device 233 may be a blood pressure meter that is configured to store as environmental measurements blood pressure data for various individuals. Each set of environmental measurements (e.g., blood pressure data) may be stored and associated with a sensor-individual correlator.

The depicted diagnostic device 233 is configured to transmit a sensor signal comprising sensor information packets to a sensor receiver 166. The sensor information packets may comprise one or more of the sensor UID, the additional stored data, the environmental measurements, and/or the sensor-individual correlator as discussed above. The sensor receiver 166 may associate some or all of the data from the sensor information packets with other stored data in the sensor receiver 166 or with data stored or received from other sensors, diagnostic devices, RF location tags 102, or reference tags. The sensor receiver 166 transmits a sensor receiver signal to a receiver hub/locate engine 108.

Another type of sensor shown in FIG. 3E is a triangulation positioner 243. A “triangulation positioner” is a type of sensor that senses position. The depicted triangulation positioner 243 includes a sensor UID, additional stored sensor data, and environmental measurements as discussed above.

In some embodiments, a triangulation positioner (also known as a global positioning system (GPS) receiver) receives clock data transmitted by one or more geostationary satellites (a satellite in a known or knowable position) and/or one or more ground based transmitters (also in known or knowable positions), compares the received clock data, and computes a “position calculation”. The position calculation may be included in one or more sensor information packets as environmental measurements.

In another embodiment, a triangulation positioner comprises one or more cameras or image-analyzers that receive emitted or reflected light or heat, and then analyzes the received images to determine the location of an individual or sensor. Although a triangulation positioner may transmit data wirelessly, it is not a RF location tag because it does not transmit blink data or a tag signal that can be used by a receiver hub/locate engine 108 to calculate location. In contrast, a triangulation positioner senses position and computes a position calculation that may then be used as environmental measurements by the receiver hub/locate engine 108.

In one embodiment, a triangulation positioner could be combined with a RF location tag or reference tag (not shown). In such embodiments, the triangulation positioner could compute and transmit its position calculation via the RF location tag to one or more receivers. However, the receiver hub/locate engine would calculate tag location based on the blink data received as part of the tag signal and not based solely on the position calculation. The position calculation would be considered as environmental measurements and may be included in associated sensor information packets.

As will be apparent to one of ordinary skill in the art, position calculations (e.g., GPS receiver position calculations) are not as accurate as the location calculations (e.g., UWB waveform based location calculations) performed by receiver hub/locate engines structured in accordance with various embodiments of the invention. That is not to say that position calculations may not be improved using known techniques. For example, a number of influences, including atmospheric conditions, can cause GPS accuracy to vary over time. One way to control this is to use a differential global positioning system (DGPS) comprising one or a network of stationary triangulation positioners that are placed in a known position, and the coordinates of the known position are stored in memory as additional stored sensor data. These triangulation positioners receive clock data from geostationary satellites, determine a position calculation, and broadcast a difference between the position calculation and the stored coordinates. This DGPS correction signal can be used to correct for these influences and significantly reduce location estimate error.

Another type of sensor shown in FIG. 3E is a proximity detector 253. A “proximity detector” is a type of sensor that senses identity within an area (e.g., a local area) that is small with respect to the monitored area 100 of FIG. 1. Many different ways of sensing identity (e.g., a unique ID or other identifier for a sensed object or individual) would be apparent to one of ordinary skill in the art in view of this disclosure including, without limitation, reading a linear bar code, reading a two-dimensional bar code, reading a near field communication (NFC) tag, reading a RFID tag such as a UHF tag, HF tag, or low frequency tag, an optical character recognition device, a biometric scanner, or a facial recognition system.

In some embodiments, a proximity detector senses an attribute of an individual (or an individual's wristband, tag, label, card, badge, clothing, uniform, costume, phone, ticket, etc.). The identity sensed by a proximity detector may be stored locally at the proximity detector 253 as shown and transmitted as environmental measurements via one or more sensor information packets to a sensor receiver 166.

In some embodiments, a proximity detector 253 may have a defined position, which is often stationary, and may be associated with a location in the monitored area 100 of FIG. 1. For example, a proximity detector 253 could be located at a finish line of a race track, an entrance gate of a stadium, with a diagnostic device, at a goal line or goal post of a football field, at a base or home plate of a baseball diamond, or a similar fixed location. In such embodiments where the proximity detector is stationary, the position coordinates of the proximity detector and a sensor UID could be stored to a monitored area database (not shown) that is accessible by one or more of the receivers 106, 166, the receiver hub/locate engine 108, and/or other components of the receiver processing and analytics system 110. In embodiments where the proximity detector is movable, a position calculation could be determined with a triangulation positioner, or the proximity detector could be combined with a RF location tag and located by the receiver hub/locate engine 108. While shown as separate fields for illustration purposes in FIG. 3E, identify information and position calculation could comprise part of the additional stored sensor data, the environmental measurements, or both.

In one embodiment, the proximity detector could be associated with a reference tag (e.g., tag 104 of FIG. 1) whose position is recorded in the monitored area database. In other embodiments, the proximity detector is movable, such that it may be transported to where it is needed. For example, a proximity detector 253 could be located on a medical cart, first down marker, a diagnostic device, goal post, or carried by a paramedic or security guard. In an embodiment where the proximity detector 253 is movable it would typically be associated with a RF location tag or triangulation positioner so that location (for a RF location tag) or position (for a triangulation positioner) can be determined at the time identity is sensed.

In the embodiment where the proximity detector includes a RF location tag, the receiver hub/locate engine 108 would locate the associated RF location tag, and the tag data/sensor data filter 112 would associate the tag location data for the associated RF location tag as the position of the proximity detector, while determining the identity of an associated individual from any received sensor information packets. In the alternate embodiment where the proximity detector includes a triangulation positioner, the triangulation positioner would compute a position calculation that could be stored as additional stored sensor data and/or environmental measurements, and transmitted as one or more sensor information packets. In one embodiment, sensor information packets for a proximity detector may include both sensed identity information and a position calculation.

Another type of sensor shown in FIG. 3E is a proximity label 263. A proximity label has a fixed position and an identification code (e.g., a sensor UID). The proximity label 263 may further comprise additional stored sensor data as shown. The depicted proximity label 263 is configured to be read by proximity detector 253. In some embodiments, proximity detector 253 may be further configured to write information to proximity label 263.

A proximity label 263 may be a sticker, card, tag, passive RFID tag, active RFID tag, NFC tag, ticket, metal plate, electronic display, electronic paper, inked surface, sundial, or otherwise visible or machine readable identification device as is known in the art. The coordinates of the position of the proximity label 263 are stored such that they are accessible to the receive hub/locate engine 108. For example, in one embodiment, the position coordinates of a proximity label 263 could be stored in a field database or monitored area database accessible via a network, or stored locally as additional stored data in the proximity detector 253.

In some embodiments, a position of the proximity label 263 is encoded into the proximity label 263 itself. For example, coordinates of a position of the proximity label 263 could be encoded into a passive RFID tag that is placed in that position. As another example, the coordinates of a position of the proximity label 263 could be encoded into a printed barcode that is placed in that position. As another example, a proximity label 263 comprising a NFC tag could be encoded with the location “end zone”, and the NFC tag could be placed at or near an end zone at Bank of America stadium. In some embodiments, the stored coordinates of the proximity label 263 may be offset from the actual coordinates of the proximity label 263 by a known or determinable amount.

In one embodiment, a proximity label 263 such as an NFC tag may be encoded with a position. When a sensor such as a proximity detector approaches the NFC tag it may read the position, then transmit the position in a sensor information packet to the sensor receiver 166′ and eventually to the receiver hub/locate engine 108. In another embodiment, a proximity label 263 such as a barcode label may be encoded with an identification code. When a smartphone with a proximity detector (such as a barcode imager) and a triangulation positioner (such as a GPS chip, GPS application, or similar device) approaches the barcode label it may read the identification code from the barcode, determine a position calculation from received clock data, then transmit the identity and the position calculation to sensor receiver 166′ and eventually to the receiver hub/locate engine 106 as part of one or more sensor information packets.

In the depicted embodiment, triangulation positioner 243 and proximity detector 253 are each configured to transmit sensor signals carrying sensor information packets to sensor receiver 166′. The depicted sensors 243, 253, like any sensor discussed herein, may transmit sensor signals via wired or wireless communication protocols. For example, any proprietary or standard wireless protocol (e.g., 802.11, Zigbee, ISO/IEC 802.15.4, ISO/IEC 18000, IrDA, Bluetooth, CDMA, or any other protocol) could be used for the sensor signals. Alternatively or additionally, any standard or proprietary wired communication protocol (e.g., Ethernet, Parallel, Serial, RS-232, RS-422, USB, Firewire, I²C, etc.) may be used. Similarly, sensor receiver 166′, and any receiver discussed herein, may use similar wired and wireless protocols to transmit receiver signals to the receiver hub/locate engine.

In one embodiment, upon receiving sensor signals from the triangulation positioner 243 and the proximity detector 253, the sensor receiver 166′ may associate some or all of the data from the received sensor information packets with other data stored to the sensor receiver 166′, or with data stored or received from other sensors (e.g., sensor 203, audio sensor 105), diagnostic devices 233, RF location tags 102, or RF reference tags 104. Such associated data is referred to herein as “associated sensor data”. In the depicted embodiment, the sensor receiver 166′ is configured to transmit some or all of the received sensor information packets and any associated sensor data to the receiver hub/locate engine 108 at part of a sensor receiver signal.

In one embodiment, a smartphone comprising a proximity detector (such as a barcode imager) and a triangulation positioner (such as a GPS chip) may associate an identification code determined from a barcode with a position calculation from received clock data as associated sensor data and transmit a sensor information packet that includes such associated sensor data to the receiver hub/locate engine 108. In another embodiment, the smartphone could transmit a first sensor information packet including the identification code and the smartphone's unique identifier to another sensor receiver, the smartphone could transmit a second sensor information packet including the position calculation and the smartphone's unique identifier to the sensor receiver, and the sensor receiver could associate the position calculation with the identification code based on the common smartphone unique identifier and transmit such associated sensor data to the receiver hub/locate engine 108. In another embodiment, the sensor receiver could determine a first time measurement associated with the first sensor information packet and a second time measurement associated with the second sensor information packet that, in conjunction with the sensor UID, could be used, by the receiver hub/locate engine 108, to associate the first sensor information packet with the second sensor information packet.

In one embodiment, the receiver hub/locate engine 108 receives receiver signals from the receiver 106 and sensor receiver signals from the sensor receivers 166, 166′. In the depicted embodiment, receiver 106 may receive blink data from the RF location tag 102 and transmits to the receiver hub/locate engine 108 some or all of the blink data, perhaps with additional time measurements or signal measurements. In some embodiments, time measurements or signal measurements may be based on a tag signal received from a RF reference tag (e.g., reference tag 104 of FIG. 1). The receiver hub/locate engine 108 collects the blink data, time measurements (e.g., time of arrival, time difference of arrival, phase), and/or signal measurements (e.g., signal strength, signal direction, signal polarization, signal phase) from the receivers 106 and computes tag location data for the tags 102 as discussed above in connection with FIG. 1. In some embodiments, the receivers 106 may be configured with appropriate RF filters, such as to filter out potentially interfering signals or reflections proximate the field of play or other area to be monitored.

The receiver hub/locate engine 108 may also access stored data or clock data from local storage and from a network location. The receiver hub/locate engine 108 uses this information to determine tag location data for each RF location tag. It may also associate data derived or extracted from tag signals transmitted from one or more RF location tags with information or data derived or extracted from sensor signals transmitted from one or more sensors.

In addition to the TOA or TDOA systems previously described, other real-time location systems (RTLS) such as received signal strength indication based systems could potentially be implemented by a receiver hub/locate engine 108. Any RTLS system using RF location tags, including those described herein, could require considerable processing by the receiver hub/locate engine 108 to determine the tag location data from the blink data received from the tags. These may require time measurement and/or signal measurement in addition to blink data, which preferably includes a tag UID. In contrast, in other systems, such as global position systems (GPS) systems, location data is determined based upon the position calculation transmitted from a GPS transmitter (also referred to as a GPS receiver or GPS tag) which includes calculated information about the location where the tag was positioned (i.e., coordinates determined at the tag via satellite signal triangulation, etc.) when the position calculation was determined or stored. Thus, GPS information typically refers to additional information that is transmitted along with a GPS transmitter ID before the transmission is received by a sensor receiver.

A GPS host device or back-end server may receive the GPS information and simply parse the position calculation (as opposed to calculating the position information at the host device) and the GPS transmitter ID into a data record. This data record may be used as a GPS position calculation, or it could be converted to a different coordinate system to be used as a GPS position calculation, or it could be processed further with DGPS information to be used as a GPS position calculation.

Returning to FIG. 3C, the depicted RF location tag 202 is used to convey (sometimes called backhaul) sensor information packets to a receiver 106. In some embodiments, while not shown, multiple sensors 203 may transmit sensor signals carrying sensor information packets to RF location tag 202. Such received sensor information packets may be associated with blink data that is transmitted to receiver 106.

In one embodiment, the receiver hub/locate engine 108 may parse sensor information packets from received tag data packets and associate such sensor information packets with the RF location tag 202 that transmitted the sensor information packet. Thus, the receiver hub/locate engine 108 may be able to determine tag location data, which may comprise a location and other data (e.g., tag data, tag UID, tag-individual correlator, sensor-individual correlator, additional stored sensor data, environmental measurements (e.g., audio data), tag-sensor correlator, identity information, position calculation, etc.) from one or more tags or sensors. Such data and information may be transmitted to the receiver processing and analytics system 110.

In some embodiments, once the receiver hub/locate engine 108 determines a location estimate of a RF location tag 102 at the time epoch of the tag signal, the receiver hub/locate engine 108 can also associate a location estimate with the tag data packet included in the blink data of such tag signal. In some embodiments, the location estimate of the tag signal may be used as tag location data for the tag data packet. In some embodiments a Geographical Information System (GIS) may be used by the receive hub/locate engine 108 to refine a location estimate, or to map a location estimate in one coordinate system to a location estimate in a different coordinate system, to provide a location estimate for the tag data packet.

In one embodiment, the location estimated for the tag data packet may be associated with any data in the tag data packet, including a tag UID, other tag data, and, if included, one or more sensor information packets, including sensor UID, additional stored sensor data, and environmental measurements. Since environmental measurements may include a position calculation from a triangulation positioner (e.g., a GPS device), the receiver hub/locate engine 108 could parse the position calculation and use it to refine a location estimate for the tag data packet.

Preferably, the receiver hub/locate engine 108 may access an individual database to determine tag-individual correlators or sensor-individual correlators. Individual data (e.g., an individual profile) may be stored in a server, in tag memory, in sensor memory, or in other storage accessible via a network or communication system, including tag data or additional stored sensor data as explained previously.

In some embodiments, by comparing data accessed using a sensor-individual correlator, the receiver hub/locate engine 108 may associate an individual with a sensor information packet received from a sensor, and/or may associate an individual with such sensor. Because the receiver hub/locate engine 108 may associate a sensor position estimate with a sensor information packet, the receiver hub/locate engine 108 may also estimate an individual position for the associated individual.

In another embodiment, by comparing data accessed using a tag-sensor correlator, the receiver hub/locate engine 108 may associate a sensor with a tag data packet received from a RF location tag 102. Because the receiver hub/locate engine 108 may associate a location estimate with a tag data packet, the receiver hub/locate engine 108 may also create a sensor location estimate for the associated sensor. By comparing a location estimate for a RF location tag with a sensor location estimate or a sensor position estimate, the receiver hub/locate engine 108 may associate a RF location tag with a sensor, or may associate a tag data packet with a sensor information packet. The receiver hub/locate engine 108 could also determine a new or refined tag-sensor correlator based on this association.

In still another embodiment, by comparing a location estimate for a RF location tag with an individual location estimate or an individual position estimate, the receiver hub/locate engine 108 may associate a RF location tag with an individual, or may associate a tag data packet with an individual. The receiver hub/locate engine 108 could also determine a new or refined tag-individual correlator based on this association.

In one embodiment, by comparing a location estimate for a sensor with an individual location estimate or an individual position estimate, the receiver hub/locate engine 108 may associate a sensor with an individual, or may associate a sensor information packet with an individual. The receiver hub/locate engine 108 could also determine a new or refined sensor-individual correlator based on this association.

Data derived or extracted from tag signals transmitted from one or more RF location tags is referred to herein as “tag derived data” and shall include, without limitation, tag data, tag UID, tag-individual correlator, tag-sensor correlator, tag data packets, blink data, time measurements (e.g. time of arrival, time difference of arrival, phase), signal measurements (e.g., signal strength, signal direction, signal polarization, signal phase) and tag location data (e.g., including tag location estimates). Tag derived data is not derived by the RF location tag, but rather, is derived from information transmitted by the RF location tag. Information or data derived or extracted from sensor signals transmitted from one or more sensors is referred to herein as “sensor derived data” and shall include, without limitation, sensor UID, additional stored sensor data, sensor-individual correlator, environmental measurements, sensor information packets, position calculations (including sensor position estimates), position information, identity information, tag-sensor correlator, and associated sensor data. Information or data derived or extracted from audio sensor signals transmitted by one or more audio sensors is referred to herein as “audio data” and shall include without limitation, audio sensor UID, additional stored audio sensor data, audio sensor-individual correlator, audio sensor information packets, tag-audio sensor correlator, and associated audio sensor data. Data derived or extracted from stored individual data is referred to herein as “individual profile information”, “participant profile information”, or simply “profile information” and shall include, without limitation tag-individual correlator, sensor-individual correlator, identity information, name, uniform number and team, biometric data, tag position on individual. In various embodiments, the receiver hub/locate engine 108 may transmit tag derived data, sensor derived data, individual profile information, various combinations thereof, and/or any information from the GIS, the field database, the monitored area database, and the individual database to the receiver processing and analytics system 110.

Example Receiver Hub and Receiver Processing and Distribution System

FIG. 4 illustrates an exemplary system 300 for providing performance analytics in accordance with some embodiments of the present invention. The depicted performance analytics system 300 may be distributed in a receiver hub 108 and a receiver processing and distribution system 110 of the type depicted in FIG. 1. For example, locate engine 302 may be part of the receiver hub 108 with the tag ID/Filter 304 through event engine 322 forming part of the receiver processing and distribution system 110. In alternative embodiments, the performance analytics system 300 may be housed or located in a single housing or unit. In still other embodiments, the performance analytics system 300 may be distributed among multiple additional housings or units depending upon the application and other design parameters that will be apparent to one of ordinary skill in the art in view of this disclosure.

The performance analytics system 300 of FIG. 4 may include a plurality of tags 102, sensors 203, and/or audio sensors 105, associated with participants (e.g., players, officials, balls, field markers, etc.), a plurality of receivers 106 positioned within a monitored environment, a receiver hub/locate engine 302, one or more filters 304, a plurality of databases, a plurality of processing engines, and a plurality of output systems. For illustration purposes, FIG. 4 depicts audio sensor 105 separately from sensor 203; however, as discussed above, audio sensor 105 is simply one type of sensor 203.

While only one type of receiver 106 is shown in FIG. 4, other types of receivers, e.g., sensor receivers 166, 166′ of FIG. 3E, may be used in accordance with the embodiments discussed herein. The one or more databases may include databases for tag identifiers 354, player roles 308, player dynamics or kinetics models 310, GIS data or a GIS database 313, field data or a field knowledge database 314, formation models 316, play models 320, audio profiles 321, event models 323, official roles 326, official models 328, ball models 332, weather data 375, or the like. The plurality of processing engines may include a player dynamics engine 306, a team formation engine 312, a play engine 318, an event engine 322, an official dynamics engine 324, a field marker engine 334, a ball engine 330, and a model generation engine 338, or the like. The system 300 may further include a game clock 380 and a universal clock 385.

In an exemplary performance analytics system 300, such as illustrated in FIG. 4, the plurality of tags 102 (and sensors 203 and/or audio sensors 105) may be attached to a participant and fixed locations as discussed in connection with FIGS. 2A-C. In some embodiments, the plurality of tags 102, sensors 203, and/or audio sensors 105 may be activated and deactivated as needed, such as before and after a game or when damaged or to replace batteries, power suppliers, local memory, etc. Each of the tags 102 may transmit a tag signal, which may include tag derived data, which is received by one or more of the receivers 106. In some embodiments, the receivers 106 may be configured with appropriate RF filters, such as to filter out potentially interfering signals or reflections proximate the field of play or other environment to be monitored.

Each of the receivers 106 may receive tag derived data from the tags 102 and transmit the tag derived data to the receiver hub/locate engine 302. The receiver hub/locate engine 302 collects the tag derived data from the receivers 106 and computes tag location data (based on the blink data) for the tags 102 as discussed above in connection with FIG. 1.

In the depicted embodiment, each of the receivers 106 receives sensor derived data from sensor signals transmitted by sensors 203 and audio data from audio sensor signals transmitted by audio sensors 105. In other embodiments, sensor receivers (e.g., sensor receivers 166, 166′ of FIG. 3E) may transmit sensor signals comprising sensor derived data and audio signals comprising audio data to the receiver hub/locate engine 302.

The tag location data, tag derived data, sensor derived data (including audio data) may be provided from the receiver hub/locate engine 302 to a tag ID/filter 304 that determines the type of participant associated with each received unique tag ID (and/or sensor ID) and routes the associated tag derived data (and optionally, other received tag/sensor derived/audio data) to one or more engines associated with such participant type (e.g., player, ball, official, field marker, etc.). In one embodiment, the tag ID/filter 304 performs this routing, at least in part, by correlating the received unique tag ID (and/or sensor ID) to profile data or prior correlations (i.e., tag ID No. 0047 is correlated to participant John Smith—quarterback, sensor ID No. 12459 is correlated to Marcus Henderson—official, etc.) that may be stored to a tag/sensor identification database 354 (i.e., tag-individual correlators, sensor-individual correlators, tag-sensor correlators, etc.). In some embodiments, the receivers 106 may also receive sensor derived data for other sensors 203, such as through the tags 102 or through separate transmission means.

In one embodiment, perhaps in connection with the player illustration of FIG. 2A, the tag ID/filter 304 identifies tag location data associated with a player and thus routes such data to a player dynamics engine 306 for further processing. The player dynamics engine 306 is disposed in communication with a player role database 308, which comprises player role data correlating tag and sensor UIDs to player profiles (e.g., individual profile information) including, without limitation, which roles (e.g., quarterback, running back, flanker, slot receiver, tight end, left tackle, left guard, center, right guard, right tackle, defensive end, defensive tackle, nose tackle, inside linebacker, outside linebacker, free safety, strong safety, cornerback kicker, punter, etc.) the players perform during a game.

The player dynamics engine 306 may also be disposed in communication with a dynamics/kinetics model database 310. The player dynamics engine 306 may compare the tag location data, other tag and sensor derived data, and player role data to player dynamics/kinetics models to determine aspects of the player dynamics or movement kinetics. The dynamics/kinetics model database 310 may comprise models of different aspects or dimensions that may be based on past player location data or other data generated by the model generation engine 338 as discussed below. The models may include, without limitation, models for a particular player profile (e.g., John Smith), a player type (e.g., quarterback), a player type for a particular team (e.g., a quarterback from the Chicago Wizards), a player type for a particular formation (e.g., a quarterback in a spread offense), and the like. Such models may consider all three dimensions (x, y, z) of the tag location data for each tag (e.g., 102 of FIG. 2A) and may further consider different tag position arrays (e.g., two tag implementations—one proximate each shoulder as in FIG. 2A, eleven tag implementations—one proximate each shoulder, one proximate each elbow, one proximate each hand, one proximate each knee, one proximate each foot, and one proximate the head).

In one embodiment, the player dynamics engine 306 determines a multi-dimensional player location per unit time (e.g., participant location data) for each player based on the tag location data, other tag and sensor derived data, the player role data, and the player dynamics/kinetics models. Such multi-dimensional player location may include relative location of the player relative to the field of play, and/or general orientation of the player (e.g., standing, squatting, laying the ground, sitting, etc.) such as by correlating location data and other tag and sensor derived data.

The player dynamics engine 306 uses the real time tag location data stream from the locate engine 302, as well as the player role database 308 to provide accurate information about what a particular player is doing in real time (or near real time). The player dynamics engine 306 may further use other tag and sensor derived data, received from the locate engine 302 in the depicted embodiment, to aid in determining not only where the player is, but also how that player's location is changing with time, velocity, acceleration, deceleration, orientation, or the like. The player dynamics engine 306 outputs multi-dimensional player location information per unit time (e.g., participant location data).

In one embodiment, sensor derived data may comprise accelerometer data that may indicate that a player (or portion of a player) is accelerating or decelerating. In addition to the variety of other uses that will be apparent to one of ordinary skill in the art in view of this disclosure, the accelerometer data may be used to improve location accuracy for the system. For example, in circumstances where the real time tag location data stream erroneously suggests (perhaps due to interference, multipath effects, signal reflections, signal losses due to line-of-sight blockages, etc.) that one of the possible locations for the player is 10 feet away from a prior location, the accelerometer data could be used to confirm that the player (or accelerometer affixed portion of the player) did not experience an acceleration sufficient to move that distance in the amount of time provided.

In some embodiments, sensor derived data may comprise time-of-flight sensor data, which may indicate distances between participants (e.g., distance of a player to other players, officials, the ball, etc.) or other objects. In applications involving complex tagged object movements such as, the example football application discussed herein, time-of-flight sensor data may be used to enhance the location accuracy of the system especially in circumstances where one or more tags or sensors are temporally unable to effectively transmit their data to one or more receivers. For example, in one embodiment, a tag positioned within the ball may appear to the system as not moving because the running back carrying the ball has run into a group of other players and the bodies of such other players are actually blocking the line-of-sight transmissions of the ball tag. In this embodiment, time-of-flight sensors positioned on the group of other players may be repeatedly determining and transmitting to one or more receivers the relative distance between such time-of-flight sensors and the ball or ball carrier. In this regard, the system may determine that the ball is no longer at the ten yard line (i.e., the point where the system last received a transmission directly from the ball tag) but rather has advanced toward the opponent's end zone to the six yard line. This and other similar techniques may be used alone or in combination with other tag and sensor derived data (e.g., accelerometer data, etc.) to create a type of mesh network that may adapt to temporary or sustained line-of-sight blockages and improve the accuracy of location determinations, formation determinations, play determinations, etc.

In some embodiments, the player dynamics engine 306 outputs multi-dimensional player location information per unit time to an event engine 322. In some embodiments, the multi-dimensional player location information may include a ranked or weighted list of probable player locations while, in other embodiments, the multi-dimensional player location information includes only a top, or most probable, player location. This information may be used by the event engine 322 to determine a number of important player events. For example, the multi-dimensional player location information may be used to indicate that a player was tackled (i.e., experienced a rapid deceleration and transited from a standing to a laying position) and is subsequently limping (e.g., tag and/or sensor data from tags/sensors proximate the players feet indicate a change in the gait of the player). In such example, the event engine 322 may be configured to transmit an alert (e.g., via text message, email, or the like) to an athletic trainer to have the player checked-out or treated.

The player dynamics engine 306 may further output the multi-dimensional player location information per unit time (e.g., participant location data) to a team formation engine 312. The team formation engine 312 is disposed in communication with a formation models database 316 that contains models of various formations (e.g., offensive formations, defensive formations, special teams formations, etc.) defined for the relevant sport or activity (e.g., football in the depicted embodiment). The models of various formations may be derived from multi-dimensional player location information collected during prior games, practices, etc., (e.g., learned by the system) or as input by one or more teams, such as by using model generation engine 338, historical data store 336, and/or team analytics engine 346.

The team formation engine 312 is further disposed in communication with a field data database 314 to assist in determining the likely team formations. The field data database 314 may comprise, without limitation, survey data for the field (e.g., various distances or coordinates from reference tag(s) or other marker to yard lines, end zones, goal posts, boundaries, benches, locker rooms, spectator areas, other zones of interest, etc.).

In one embodiment, the team formation engine 312 determines one or more formations (e.g., a probable formation or a ranked or weighted list of probable formations) based at least in part on the field data, the multi-dimensional player location information (which may include the tag derived data and/or sensor derived data), and the formation models. The team formation engine 312 may hypothesize the received multi-dimensional player location data against models of every known formation to determine a probable formation or a ranked or weighted list of probable formations. The team formation engine 312 is thus configured to determine and output a data stream of formations versus time, which considers how various formations change and may be used by downstream engines to determine various events including the occurrence of a play.

In one embodiment, the team formation engine 312 may assign weights to the received multi-dimensional player location data (i.e., participant location data), other types of tag derived data and/or sensor derived data, and/or to the formation models when determining a specific formation or ranked list of probable formations. For example, in one embodiment, the team formation engine 312 may be configured to assign a greater weight to the position of the ball (which should remain stationary for a period of time as formations are being established, i.e., at the beginning of a play) than to the position of an official (which may move to some degree as formations are forming). In another embodiment, the team formation engine 312 may be configured to assign a greater weight to the location of the tight-end (which may indicate the strong side of a formation) than to the location of a left guard (whose location seldom effects formation determination). In still another embodiment, the team formation engine 312 may be configured to assign a greater weight to sensor derived data associated with an accelerometer positioned proximate an official's wrist (which may indicate winding of the play clock that often triggers the period during which formations ought to be forming) than to the location of any player.

In one embodiment, the team formation engine 312 outputs the data stream of formations versus time (e.g., formation data) to the play engine 318. The play engine 318 may also receive the output data stream (e.g., multi-dimensional player location information versus time) from the player dynamics engine 306 and audio data from the tag ID/filter 304. The play engine 318 is disposed in communication with a play models database 320 and an audio profile database 321. The play models database 320 may include play models (e.g., known formation shifts or movements over time). Such play models may be programmatically learned by the system (e.g., based on actual movements of players tracked by the system) or manually entered through an interface or other tool (e.g., perhaps through the model generation engine 338). In this regard, the play models database 320 may include historical plays executed by teams, potential/future plays from a team game plan or playbook, or other historical data (e.g., from historical data store 336). The audio profile database 321 may include audio profiles (e.g. known audio patterns over time). Such audio profiles may be programmatically learned by the system (e.g. based on actual audio data tracked by the system) or manually entered through an interface or other tool (e.g. perhaps the model generation engine 338). In this regard the audio profile database 321 may include audio profiles of historical plays

In one embodiment, the play engine 318 may compare the audio data received from the location engine 302 and the audio profiles to determine whether a play is forming, a play has started, a play is in progress or a play has ended. For example the play engine 318 may determine that a play is forming based on audio profiles which may include a play calls players talking, or the like. The play engine 318 may thereafter determine play has started based on audio profiles which may include an official whistle, a quarterback cadence, a silence (e.g. ambient noise) followed by a snap, or the like. The play engine 318 may determine a play is in progress based on audio profiles which may include impact noises, shouting, or the like. The play engine 318 may determine that a play has ended based on audio profiles which may include an official whistle, official call, or the like.

In one embodiment, the play engine 318 may take the formations versus time data stream from the formation engine 312, the play models, and the player dynamics data stream (which may include tag location data and/or other tag and sensor derived data) to determine whether a play is forming, a play has started, a play is in progress, or a play has ended. For example, the play engine 318 may determine that it is most likely that a pre-snap formation at the line of scrimmage has occurred (e.g., an offensive team has aligned in a “pro set” formation and a defensive team has aligned in a “3-4” formation) indicating a play is about to begin. The play engine 318 may thereafter determine that the offensive and defensive players have begun rapidly accelerating towards and across a line of scrimmage thereby indicating that a play has begun. The play engine may further determine that an offensive player has been tackled by a defensive player thereby indicating that a play has concluded.

The play engine 318 may improve the event determination by additionally analyzing for audio data and audio profiles, alone or in conjunction with, the player models and player dynamic data stream. The play engine 318 may determine an event such as the play start and stop times based on audio data alone, by comparing the audio data to an audio profile and assigning a probability value. In an instance in which the probability value satisfies a predetermined threshold an event is determined. For example, an 80 percent probability of an official whistle, indicating play start, quarterback cadence and impact noises indicating play in progress, and an official whistle to indicate the play has concluded, may satisfy a predetermined threshold of 75 percent.

In another embodiment, the play engine 318 may synchronize the time stamps of the audio data and the location data for analysis. The play engine 318 may compare the audio data to audio profiles correlated to play models and assign a probability to each compared audio profile and play model. If the probability value satisfies a predetermined value an event may be determined. For example, the play engine 318 may determine in an instance in which the players move toward the line of scrimmage in conjunction with play calls and player talking. The play engine 318 may determine in an instance in which it is most likely that a pre-snap formation at the line of scrimmage has occurred (e.g., an offensive team has aligned in a “pro set” formation and a defensive team has aligned in a “3-4” formation) indicating a play is about to begin in conjunction with an official whistle and a quarterback cadence. The play engine 318 may thereafter determine that the offensive and defensive players have begun rapidly accelerating towards and across a line of scrimmage in conjunction with an official whistle and quarterback cadence thereby indicating that a play has begun. The play engine 318 may further determine that an offensive player has been tackled by a defensive player in conjunction with impact noise and an official whistle thereby indicating that a play has concluded.

In some embodiments, the play engine 318 may use assigned weights (or assign weights) to the received data (e.g., the tag derived data, the sensor derived data, the multi-dimensional player location data, the formations data, officials data, etc.) for use in analyzing the data and determining the most probable play events. For example, the play engine 318 may determine that data for particular participants (e.g., a left guard) has a lower relevance for a particular formation (e.g., a pro set offensive formation) and assign a lower weight to that data during the analysis than to another participant (e.g., the ball, the quarterback, a wide receiver, etc.).

In some embodiments, the play engine 318 is disposed in communication with an official dynamics engine 324 to further improve the play determination accuracy of the system. The official dynamics engine 324 may provide data about the movements, actions, positions of an official, which the play engine 318 may use when determining a probable play and/or the status of a play. For example, as discussed in connection with FIG. 2B above, an official may be provided with wrist based accelerometers or other sensors (e.g., a whistle sensor), which may be used to flag the beginning or ending of a given play based on the movement or action of an official (e.g., rotating an arm to wind the play clock, indicate touchdown with two arms raised, blow a whistle, etc.).

The play engine 318 may improve the play determination accuracy by analyzing audio data in conjunction with official dynamics data. The sensor data based on call movements, blowing a whistle, or throwing a flag may be analyzed with audio data correlating to an official whistle (removing discrepancies in an instance in which an official may place the whistle in their mouth, but not blow or sound the whistle), an official call, or official to official discussions.

The play engine 318 may analyze how the team formations occur and how they break up to determine both start and stop of a play (e.g., start of play event, end of play event, etc.). For example, the play engine 318 may determine that offensive and defensive formations coalesced proximate a line of scrimmage and then broke up with various receivers heading towards the defensive team's end zone, there was all kinds of activity around a quarterback which eventually dissipated, and that defense players were tracking one of the receivers downfield until the receiver crossed into the end zone and an official raised his arms. The play engine 318 may determine that this participant activity best fits a play model whereby a ball was thrown and caught by a receiver who then scored a touchdown thereby ending the play. The play engine 318 may improve the determination of a play by analyzing audio data which may include crowd noise consistent with scoring, failing to score first down, or the like. For example, the crowd noise may be loud and excited (e.g. higher relative frequency) for scoring or first down and swell and then fall for a failure to score a touchdown.

In some embodiments, the play engine 318 may hypothesize the received multi-dimensional player location data (e.g., participant location data) and the data stream of formations versus time against models of every known play to determine a probable play or a ranked list of probable plays. The play engine 318 is thus configured to determine and output a data stream of plays versus time, which may be communicated to the event engine 322.

In some embodiments, the tag ID/filter 304 may determine that received tag derived data and/or sensor derived data (including audio data) corresponds to one or more officials. Such official correlated tag/sensor derived data is routed to the official dynamics engine 324. The official dynamics engine 324 is disposed in communication with an official roles database 326, which comprises official roles data correlating tag and sensor IDs (or other tag/sensor individual correlators) to official profiles including, without limitation, which roles (e.g., referee, umpire, head linesman, line judge, back judge, field judge, side judge, etc.) the officials perform during a game.

The official dynamics engine 324 may also be disposed in communication with a dynamics/kinetics model database 328. The official dynamics engine 324 may compare the tag location data, other tag/sensor derived data, and official role data to official dynamics/kinetics models to determine aspects of the official dynamics or movement kinetics. The dynamics/kinetics model database 328 may comprise models of different aspects or dimensions that may be based on past official location data or other data generated by the model generation engine 338 as discussed below. The models may include, without limitation, models for a particular official profile (e.g., Ralph Stevens), an official type (e.g., referee), an official type for a particular foiniation (e.g., a referee positioned during a kickoff), and the like. Such models may consider all three dimensions (x, y, z) of the tag location data for each tag (e.g., 102 of FIG. 2B) and may further consider different tag position arrays (e.g., two tag implementations—one proximate each shoulder as in FIG. 2B, eleven tag implementations—one proximate each shoulder, one proximate each elbow, one proximate each hand, one proximate each knee, one proximate each foot, and one proximate the head).

In one embodiment, the official dynamics engine 324 determines a multi-dimensional official location per unit time for each official based on the tag location data, other tag and sensor derived data, the official role data, and the official dynamics/kinetics models. Such multi-dimensional official location may include (1) a relative location of the official relative to the field of play, (2) a general orientation of the official (e.g., standing, squatting, laying the ground, sitting, etc.), and (3) a specific orientation of the official (e.g., arms raised, arms at hips, one hand grasping the wrist of the other arm, etc.).

The official dynamics engine 324 uses the real time tag location data stream from the locate engine 302, as well as the official role database 326 to provide accurate information about what a particular official is doing in real time (or near real time). The official dynamics engine 324 may further use tag and sensor derived data, received from the locate engine 302 in the depicted embodiment, to aid in determining not only where the official is, but also how that official's location is changing with time, velocity, acceleration, deceleration, orientation, or the like. For example, in one embodiment, the sensor derived data may comprise accelerometer data that may indicate that an official (or portion of an official) is accelerating or decelerating. The official dynamics engine 324 outputs multi-dimensional official location information per unit time. Such multi-dimensional official location information may include information regarding the official's location, how the location is changing with time, orientation of the official, motions or gestures of the official, or the like.

In some embodiments, the tag ID/filter 304 may determine that received tag and/or sensor derived data corresponds to the game ball (e.g., a ball such as the ball shown in FIG. 2C, which is used or capable of use in the field of play). Such ball correlated tag/sensor derived data is routed to the ball dynamics engine 330. While the ball engine 330 is not shown in communication with a “roles” database as in the case of some of the other processing engines, one of ordinary skill in the art will readily appreciate some ball role data may be used, such as a ball ID or the like, indicating that the received tag/sensor derived data is associated with a given ball.

The ball engine 330 may access a ball models database 332, which comprises data indicating how location data and other tag and sensor derived data correlates to particular ball events during play. The ball engine 330 may provide information regarding the ball's position/location (vertical and/or horizontal), how the location is changing with time, the velocity of the ball, the rotation of the ball, or the like for determining events during play. The ball engine 330 may output ball data streams to the event engine 322. In some embodiments, although not shown in FIG. 3, the ball engine may also output a data stream to other processing engines for analysis, such as to the play engine 318 for use in determining status of a play.

In some embodiments, the tag ID/filter 304 may determine that received tag and/or sensor derived data corresponds to a field marker (e.g., penalty flags, line of scrimmage markers, yards to gain markers, and the like). The tag ID/filter 304 may then route such field marker correlated tag/sensor derived data to a field marker engine 334 for further processing. The field marker engine 334 may provide information regarding field marker location, how the location is changing with time, or the like, for determining events during play. The field marker engine 334 may output data streams to the event engine 322. In some embodiments, although not shown in FIG. 3, the field marker engine may also output a data stream to other processing engines for analysis, such as to the play engine 318 for use in determining the status of a play or play event.

In some embodiments, a game clock 380 may be provided that is configured to keep an official time for a game or other tracked activity. In applications such as the depicted football application, the game clock is configured to count down from some standard period or quarter length (e.g., 15 minutes) and may be periodically stopped or started by one or more officials and/or the game operations system 342 as discussed in greater detailed below. While not separately illustrated in FIG. 3, the game clock 380 may further include a play clock, shot clock, pitch clock, or the like, which depending upon the application, may also be started and stopped by one or more officials and/or the game operations system 342.

The universal clock 385 provides a system time for the performance and analytics system 300. As will be apparent to one of ordinary skill in the art in view of this disclosure, the universal clock 385 is running clock for tracking, cataloging, and calibrating system actions, processes, and events. For illustrations purposes, the game clock 380 and the universal clock are shown as inputs for the event engine 322; however, in other embodiments, such clocks may provide inputs to any or all of the player dynamics engine 306, the team formation engine 312, the play engine 318, the event engine 322, the official dynamics engine 324, the field marker engine 334, the ball engine 330, and the model generation engine 338.

An event engine 322 may receive the outputs from the player dynamics engine 306, the team formation engine 312, the play engine 318, the audio profile database 321, the event model database 323, the official dynamics engine 324, the ball engine 330, the field marker engine 334, the weather data store 375, a game clock 380, and a universal clock 385 to determine events occurring during game play or to perform analytics, including predictive analytics, on game related data. In some embodiments, the event engine 322 determines such events and performs such analytics by comparing its received inputs to a historic data store 336 containing past events or analytics. In some embodiments, the event engine 322 outputs event data streams (e.g., one or more output events) to a number of systems including, without limitation, a visualization system 340, a game operations system 342, a camera control system 344, a team analytics system 346, a league analytics system 348, a statistics system 350, an XML feed and/or instant message feed 352, a historical data store/engine 336, or other systems as may be apparent to one of ordinary skill in the art in view of this disclosure.

In some embodiments, the event engine 322 may use audio data to determine if audio data correlates to an event audio profile. The event engine 322 receives the audio data from the locate engine 302 and event audio profiles from the event model database 323 to determine if an event has occurred. The event engine 322 may compare the audio data to audio profiles and assign a probability to each compared audio profile. If the probability satisfies a predetermined value an event may be determined, or the event engine 322 may further compare participant location data to event models.

In an instance in which an event determination includes both audio data and participant location data the event engine 322 may request the appropriate time stamp from the game clock 380 and universal clock 385. The universal and/or game time is associated with the audio data and participant location data. The play engine may further cross check the universal/game time stamp with time stamp from the tag locate engine 302 to increase accuracy. The event engine 322 may synchronize the participant location data and the audio data. Once synchronized the event engine 322 analyzes the participant location data in conjunction with the event audio profile to determine an event.

The event engine 322 may compare the selected event audio profile, player dynamics, team formations, play models, official dynamics, ball data, field marker data, weather data, audio data, or the like to event models and assigns a probability value to each compared event model and assign a probability value. The event model may include, but not limited to participants on field, roles of participants, locations of participants, formations of participants, audio profile, field marker location, or the like. If the event model probability satisfies the predetermined value an event is generated. A event may comprise start and end time of the play, duration of the event, number and specific participants of the event, formation and dynamic paths of the event, weather conditions, field positions and change to field positions for each participant, downs, change in ball position, and the like.

In some embodiments the event engine outputs the event to a number systems including, without limitation, a visualization system 340, a game operations system 342, a camera control system 344, a team analytics system 346, a league analytics system 348, a statistics system 350, an XML feed and/or instant message feed 352, a historical data store/engine 336, or other systems as may be apparent to one of ordinary skill in the art in view of this disclosure.

In some embodiments, the event engine 322 may output event data streams that include the time delay between tag and/or sensor transmissions and the determination of the events such that other processes, such as a visualization system, game operations system, etc., may properly correlate to different inputs (e.g., video recording versus the determined events) so that the different inputs are synchronized. In other embodiments, the event data streams may include time stamps (game time stamp, universal time stamp, etc.) for determined events or other system processes. In this way, the performance and analytics system 300 or some downstream system can determine, inter alia, which events or processes occurred in-game (i.e., during a running game or play clock) or out-of-game (i.e., while the game or play clock were stopped).

In various embodiments, the event data streams or output events provided by the event engine may include tag events (e.g., battery low indication, error indication, etc.), sensor events (e.g., battery low indication, error indication, etc.), locate engine events (e.g., status indications, error indications), tag ID/Filter events (e.g., status indications, error indications), player dynamics engine events (e.g., status indications, error indications), player events (e.g., player tackled indication, player injured indication, etc.), official dynamics engine events (e.g., status indications, error indications), official events (e.g., official injured indication, etc.), ball engine events (e.g., status indications, error indications), ball events (e.g., new ball required indication, etc.), team formation engine events (e.g., status indications, error indications), team formation events (e.g., formation type indication, new formation indication, illegal formation indication, etc.), play engine events (e.g., status indications, error indications), play events (e.g., play type indications such as run, pass, punt, field goal, etc., play results, and in-play or sub-play events such as bootleg, 3 step drop, 5 step drop, 7 step drop, crossing pattern, hook pattern, fly pattern, drive block, pass block, spin move, swim move, press coverage, zone coverage, etc.), or any other events that may be apparent to one of ordinary skill in the art in view of this disclosure. A variety of additional event data streams or output events are described in connection with the analytics systems and control systems discussed below.

In one embodiment, the event engine 322 outputs an event data stream to the visualization system 340 that may be used by the visualization system to provide enhanced telecasts or game experiences for television broadcasts, streaming mobile device clients, and other media outlets, gaming systems, and other computer graphics visualization systems. Such event data streams may be used to provide enhanced graphics, displays, information, visualizations, and the like. For example, and without limitation, the visualization system 340 may receive real time (or near real time) data including, without limitation, player ID, official ID, team ID, formation identifiers, play identifiers, pre-snap play probabilities, play diagrams, player route data, player speed data, player acceleration data, ball route date, ball speed data, ball acceleration data, player trend information, offensive team trend information, defensive team trend information, special teams trend information, and other tag and/or sensor derived data. In some embodiments, the visualization system 340 may be configured to provide a dynamically configurable interface that may be engaged by a user to select graphics or areas of focus. For example, in one embodiment, a user may configure the system to display possible passing lanes for a quarterback to his eligible receivers. In still other embodiments, the visualization system 340 may output a data stream for use in gaming systems, such as plays, player actions, or the like.

In gaming systems examples, the visualization system 340 may provide output of event data that may be configured for display via a gaming console or handheld device. Such visualization system outputs may, for example, provide for incorporating actual or predicted actions of a “live” player into a gaming environment. In some embodiments, the visualization system may also access stored computer generated or user created avatars for use with the event data stream.

In one embodiment, the event engine 322 outputs an event data stream to the game operations system 342 that may be used by the game operations system to coordinate, manage, or assist in the coordination or managing of game operations including, without limitation, the game clock 380 (and optionally the play clock), down and distance determination, score board operations, penalty enforcement, and the like. For example, and without limitation, the game operations system 342 may receive real time (or near real time) data from the event engine 322 including, without limitation, a clock start indication, a clock stop indication, a play start indication, a play end indication, a reset play clock indication, a 1^(st) down indication, a 2^(nd) down indication, a 3^(rd) down indication, a 4^(th) down indication, a turnover indication, a yard to gain indication, a 5 yard penalty indication, a 10 yard penalty indication, a 15 yard penalty indication, an end of quarter indication, an end of half indication, and an end of game indication.

Said differently, the event engine 322 may determine a number of events that may be output to the game operations system or other devices. Such events may include, without limitation, a ready for play event (e.g., an official has spotted the ball at the line of scrimmage and started a play clock in a football example, a pitcher has received the ball from his catcher in a baseball example, or the pins have been set in a bowling example), a start of play event (e.g., the ball has been snapped in a football example, the pitcher has begun his pitching motion or wind-up in a baseball example, or a bowler has begun his bowling motion in a bowling example), and an end of play event (e.g., the official has blown a whistle in a football example, an umpire has called a third strike in a baseball example, or the nine pins have been knocked down in a bowling example). Such events may be used to determine plays, formations, and to output play diagrams (e.g., graphs or plots of participant location versus time from a start of play event to an end of play event).

The event engine 322 may be further configured to output a play result to the game operations system 342 or other device. Such play results may include, for example and without limitation, a gain of twelve yards, a loss of three yards, an interception, a touchdown, live play, a first and subsequent downs, and the like in football embodiments; a ball, a strike, a fly-out, a single, a double, a home run, a run scored, and the like in baseball embodiments; and a gutter, a strike, a spare, and the like in bowling embodiments.

As would be apparent to one of skill in the art, the various engines and/or output systems may include security measures, such as encryption, access permissions, and the like, to secure system inputs and outputs. In some embodiments, the engines and/or output systems may comprise security measures to prevent hacking, jamming, transmission interception, etc. to prevent interference from outside parties, such as third parties attempting to gain information that may be advantageous in wagering, for example.

In one embodiment, the event engine 322 outputs an event data stream to the camera control system 344 that may be used by the camera control system to engage or transition engagement between one or more television, film, or other cameras to capture game events. For example, and without limitation, the camera control system 344 may receive real time (or near real time) data including, without limitation, an engage or disengage camera 1 indication, an engage or disengage camera 2 indication, an engage or disengage camera 3, . . . and an engage or disengage camera n indication. In some embodiments, the event engine 322 may output camera control indications (e.g., event data) based on real time (or near real time) game activity (e.g., ball location data suggests that the ball is closest to a known field of view for camera 4 and, thus, an engage camera 4 indication is transmitted to the camera control system 344). In other embodiments, the event engine 322 may output camera control indications (e.g., event data) based in part on a prediction of game activity (e.g., ball position, acceleration, and direction data suggests that the ball has just left the quarterback's hand and is being passed along a direction and at a velocity indicative of being caught in the field of view of camera 4 and, thus, an engage camera 3 indication is transmitted to the camera control system 344). In other embodiments, the camera control system 344 may provide indications such as to tilt, pan, or zoom in connection with a particular camera based on event data or predicted actions, or set a location or point of view based on where a player, formation, or play may be best viewed.

In one embodiment, the event engine 322 outputs an event data stream to the team analytics engine 346 that may be used to generate real time (or near real time) analytics (e.g., player performance information, formation performance information, play performance information, and team performance information) concerning game activity that may be useful to individual teams. For example, in one embodiment, the team analytics engine 346 may use event data to determine actual game performance versus playbook design including, without limitation, an evaluation of player routes, offensive, defensive, and special teams formations, offensive blocking protection schemes, defensive blitzing schemes, and the like.

In another embodiment, the team analytics engine 346 may use event data to determine actual game performance versus historical game performance (such as by using historical data store 336) including, without limitation, an evaluation of game performance (e.g., player, team, offense, defense, special teams, etc.) versus prior year performance, prior game performance, prior quarter performance, prior possession performance, prior play performance, and the like. In this regard, as will be apparent to one of ordinary skill in the art, the team analytics engine 346 may be used to evaluate performance (e.g., the left tackle has missed three assignments), identify trends (e.g., the defensive team consistently sends a linebacker blitz against a spread offensive formation), make player substitutions (e.g., a second string left tackle has performed better historically against the right end of the defense and thus should be substituted for the starting left tackle), revise game plans, or provide alerts (e.g., the flanker has experienced significantly reduced speed, acceleration, and performance following being tackled and thus an alert should be generated to the training staff to ensure that such player is medically evaluated).

For example, in one embodiment, a trainer may have a device, such as a handheld device, tablet, etc., that may receive alerts regarding a particular player. The trainer may receive background information and/or past information on a player as well as what change the system has identified to cause the alert, such as a change in gait, slower route running, etc. The trainer may then be able to evaluate the player and provide input to the system regarding the player evaluation, such as if further attention is required or if the player can return to play. In some embodiments, such alert and evaluation results may also be provided to the league analysis system, such as for use in determining injury trends or the like.

In some embodiments, the team analytics engine 346 may be used to alert a team (e.g., coaches) to focus on specific players who are performing sub-par versus their normal (historical) performance, such as by plays or by teams. In some embodiments, the team analytics engine 346 may further output analysis results to the historical data store 336 or the like, for use in future analysis and/or the building or updating of various models. The event engine 322 may send an event or alert to the team analytics engine 346 in response to an audio data associated with an audio profile of a scream, yell of “medic”, other identifier of player injury, or the like.

In another embodiment the team analytics engine may also correlate the audio data to the location data for review of team analytics. For example, the quarterback may yell “bravo bravo” indicating that he anticipates the defense to blitz. The team could analyze when the quarterback call was made in relation to the positions of the defensive players and the offensive players. Further, the team may be able to analyze the change in position of the offensive and defense players in response to the quarterback call.

In one embodiment, the performance and analytics system is configured to evaluate player performance by correlating at least one tag to the player; receiving blink data (and other tag derived data) transmitted by the at least one tag; determining tag location data based on the blink data; receiving player role data; comparing the tag location data to player dynamics/kinetics models based at least in part on the player role data; determining player location data based on the comparing the tag location data to the player dynamics/kinetics models; and determining player performance information based on comparing the player location data to stored player location data. In some embodiments, the stored player location data may be stored to the historical data store 336 and may include player location data for the actual player to be evaluated (e.g., Frank Smith, left tackle, #55) and/or player location data for another player (e.g., Fred Johnson, left tackle, #65) who plays a similar position to the actual player to be evaluated. In still other embodiments, the stored player location data may include competitive data based on the performance of the actual player against an opposing player (e.g., the left tackle blocked the right defense end successfully in five prior match-ups, the defensive back caused a delay by the wide receiver of 2 seconds in running a passing route by applying press coverage, etc.).

In another embodiment, the performance and analytics system is configured to evaluate official performance by correlating at least one tag to the official; receiving blink data (and other tag derived data) transmitted by the at least one tag; determining tag location data based on the blink data; receiving official role data; comparing the tag location data to official dynamics/kinetics models based at least in part on the official role data; determining official location data based on the comparing the tag location data to the official dynamics/kinetics models; and determining official performance information based on comparing the official location data to stored official location data. In some embodiments, the stored official location data may be stored to the historical data store 336 and may include official location data for the actual official to be evaluated and/or official location data for another official who held a similar position (e.g., referee, umpire, etc.) to the actual official to be evaluated.

In one embodiment, the event engine 322 outputs an event data stream to the league analytics engine 348 that may be used to generate real time (or near real time) analytics concerning game activity that may be useful to a league (i.e., a collection of teams). For example, in one embodiment, the league analytics engine 348 may use event data to improve game safety by identifying injury trends (e.g., player concussions occur at a higher rate when an offensive team runs crossing passing routes from a spread formation against a 3-4 defense, etc.). In another embodiment, the league analytics engine 348 may use event data to evaluate rule changes (e.g., a rule change intended to speed up game play is or is not achieving its intended result). In still another embodiment, the league analytics engine 348 may use event data to improve officiating (e.g., determining the accuracy of official calls). In some embodiments, the league analytics engine 348 may further output analysis results to the historical data store 336 or the like, for use in future analysis and/or the building or updating of various models.

In one embodiment, the event engine 322 outputs an event data stream to the statistics engine 350 that may be used to generate real time (or near real time) statistics concerning game activity. Such statistics may include, without limitation, offensive statistics (e.g., passing, rushing, receiving, turnovers, touchdowns scored, etc.), defensive statistics (e.g., tackles, sacks, interceptions, turnovers generated, etc.), special teams statistics (e.g., punt length, punt hang time, average return, long return, field goal accuracy, etc.), play diagrams, length of play statistics (e.g., 4.8 second average play, 22 second average pre-snap formation period, etc.), player participation statistics (e.g., John Smith participation in 42 of 68 offensive plays, etc.), summary statistics (e.g., top scorers, fantasy points, minutes on offense, etc.), official statistics (e.g., penalties called, location tracking diagrams per play, etc.) and the like. In some embodiments, the statistics engine 350 may further output statistics and results to the historical data store 336 or the like, for use in future analysis and/or the building or updating of various models.

In one embodiment, the event engine 322 outputs an event data stream to the XML feed and/or instant messaging feed engine 352 that may be used to generate XML or instant messaging data streams that may include live data such as plays, scoring plays, other scoring info, results, top scorers, summary statistics, or the like.

In one embodiment, the event engine 322 may output an event stream that may be used to annotate or tag a game recording, for example, using visualization system 340, game operations system 342, or the like. For example, in one embodiment, the event engine 322 may flag, tag, or annotate certain events (e.g., plays, penalties, formations, clock start/stop, etc.) into a video recording or live data stream of a game for later playback or analysis. In some embodiments, any event identified by the event engine 322 may be flagged, tagged, or annotated to a video or other data stream to provide for ease of later identification. In this regard, various events may be readily searched, identified, stored to a database in an indexed way, and/or analyzed.

In some embodiments, the event engine 322 may determine events occurring proximate one or more play boundaries. For example, using outputs from the player dynamics engine 306, the ball engine 330, and the official dynamics engine 324 the event engine 322 may determine that a touchdown has been scored (i.e., a player has carried the ball across a goal boundary into the endzone). In particular, the event engine 322 may determine that a running back carried the ball (based on location data received from the ball engine and the player dynamics engine) across the goal boundary (based on field data), which was confirmed by the nearest official signaling touchdown by raising both arms (based on location data received from the official dynamics engine). The event engine 322 may improve the determination of an event by associating audio data to the location data. For example, the touchdown being scored may correlate with excited (e.g. relatively high frequency) crowd noise and a failure to score the touch down may correlate with a swell and fall of crowd noise.

In some embodiments, the event engine 322 may output an event data stream to a historical data store/engine 336, which may store data generated by the various processing engines over time. The historical data store/engine 336 may be accessed by various systems, such as for use in providing analytics or generating new models. For example, historical data store/engine 336 may provide historical data to model generation engine 338, which the model generation engine 338 may use in learning (or developing) new play or formation models that should be added to the respective model databases. In some embodiments, the historical data store/engine 336 may be accessed by the analytics and statistics systems to generate more in-depth analytics or statistics. In some embodiments, the historical data store 336 may comprise prior event and tag derived data received by the system for each individual player (e.g., John Smith) and may also comprise player data received from other sources, such as from manual input tools (i.e., such as using a form or template) or external data sources (e.g., other statistics databases, etc.).

In some embodiments, the event engine 322 may output an event data stream that may be used in conjunction with historical results, such as from historical data store 336, for determining odds for outcomes of various team matchups. For example, the event data stream and historical event data may be analyzed to generate and/or change predicted odds for outcomes of each play, etc., which may be used in a wagering system or the like.

In some embodiments, the team analytics system 346 may provide an interface tool (i.e., perhaps through the model generation engine 338) configured to allow a team to input future plays (i.e., a game plan). Such future plays may be tested against historical data stored to the historical data store 336 in order to determine a probability for success. For example, the team analytics system 346 may be configured to allow a team to virtually test an individual play intended to be run from a given offensive formation against defenses that were historically run against such offensive formation. As will be apparent to one of ordinary skill in the art in view of this disclosure, the team analytics system 346 may be configured to allow a team to virtually test its game plan against another team, specific players, specific formations, specific blocking protections, specific blitz packages, specific weather conditions, and the like.

In one embodiment, the team analytics system 346, or any other engine or system, may be configured with access security controls (e.g., password protection schemes, etc.) sufficient to limit access to team proprietary data (e.g., game plan information, player injury data, etc.) to individual teams. In this regard, game integrity may be preserved by ensuring that proprietary data of a first team is not obtained by a competing second team.

In some embodiments, the event engine 322 and its corresponding output systems (i.e., the visualization system 340, the game operations system 342, the camera control system 344, the team analytics system 346, the league analytics system 348, the statistics system 350, the XML feed/IM feed system 352, and the historical data store/engine 336) may be configured to provide different levels of specificity for the output data. For example, an individual team may receive output data breaking down the specific details for each play and the player dynamics for the play, such that the team may determine the performance of each player in executing the specifics of a play versus an intended design. In contrast, similar yet less detailed output may be provided to all teams such as basic play diagrams and standard statistics for the players.

In some embodiments, one or more of the engines shown in FIG. 3, such as, without limitation, the team formation engine, the play engine, the event engine, or the like, may output lists or ranked lists of probable output events (e.g., locations, formations, plays, events, etc.) for display to a user via a graphical user interface (e.g., PC, tablet, mobile device, etc.) and/or for use by downstream engines or systems. In other embodiments, the above described engines may select from the ranked list of probable events a most probable event, or more simply a “probable event” (e.g., probable location, probable formation, probable play, probable blocking technique, probable passing route, etc.), that either has the highest probability indicator among the ranked list or has a probability indicator above a pre-defined threshold.

In some embodiments, the user may validate or confirm an output event (e.g., a location, a formation, a play, or an event) to improve system operation. For example, in one embodiment, the event engine 322 may determine that the following events may have occurred each with a respective probability indicator shown in parenthesis: completed pass—12 yard gain for the offense (68%); completed pass—10 yard gain for the offense (21%); incomplete pass—0 yard gain for the offense (19%). This ranked list may be displayed to an official via a mobile device who may select and confirm the correct output event, which in this example is the completed pass for a 12 yard gain for the offense. In this regard, as will be apparent to one of ordinary skill in the art in view of this disclosure, the system may employ a user to break ties or close calls (e.g., probabilities within 10 percent, etc.) or to improve the accuracy of models, input weighting allocations, and the like.

In still other embodiments, the performance and analytics system may determine or predict participant locations, formations, plays, or other events despite temporary or sustained losses of blink data for one or more tags (e.g., due to transmission failures associated with multipath effects, line-of-sight blockages, etc.). For example, in one embodiment, the performance and analytics system: receives first tag location data for a first participant (e.g., a ball carrier) during a first time period (e.g., an in-play period representing the first 3 seconds of a play); receives subsequent first tag location data for the first participant during a second time period (e.g., a second in-play period representing the second 3 seconds of a play); receives second tag location data for a second participant (e.g., the ball carried by the ball carrier) during the first time period; and determines (or predicts) subsequent second tag location data for the second participant during the second time period based at least on: the first tag location data for the first participant during the first time period, the subsequent first tag location data for the first participant during the second time period, and the second tag location data for the second participant during the first time period.

The above determination or prediction may be further improved using tag derived data and sensor derived data. For example, the performance and analytics system may receive first sensor derived data (e.g., time-of-flight sensor data or other tag and sensor derived data suggestive of a relative proximity between the first participant and the second participant) for the first participant during the first time period; receive subsequent first sensor derived data for the first participant during the second time period; and determine the subsequent second tag location data for the second participant during the second time period further based at least on: the first sensor derived data for the first participant during the first time period, and the subsequent first sensor derived data for the first participant during the second time period.

In still other embodiments, the above determination or prediction of second participant location may be improved by comparing participant location at various times to formation and/or play models. Such comparisons may further include field data, and participant role data. For example, if we maintain the above example whereby the first participant is a ball carrier and the second participant is a ball, the performance and analytics system may determine or predict the location of the ball (i.e., in circumstances where tag or sensor transmissions from the ball are blocked) during a pre-snap period by determining that the ball carrier is aligned in a stationary location in the backfield. By comparing such ball carrier location data to formation models, the system may determine that the ball is most likely positioned at the line of scrimmage proximate the center.

Similarly, in another embodiment, perhaps where the first participant is a quarterback and the second participant is a left guard, the performance and analytics system may determine or predict the location of the left guard in any given play or time period based upon comparing movements of the quarterback to formation and play models. For example, quarterback movement from a snap position to a drop back passing position may be suggestive that the left guard is positioned in a pass blocking position proximate the line of scrimmage. Alternatively, quarterback movement from a snap position to a hand-off position may be suggestive that the left guard is positioned up field of the line of scrimmage in a run blocking position.

FIG. 5 illustrates example participant (e.g., player) tracking over time in accordance with some embodiments of the present invention. More specifically, FIG. 5 illustrates the changing position of an offensive team during game action. Such tracking of changing positions may be useful for various engines of the present system including, without limitation, the player dynamics engine, the formation engine, the play engine, and the event engine. For example, at a first time, t−1 (e.g., game clock: 12:26, play clock: 38 seconds, universal clock: 16:09:30), the tag location data may indicate that the tracked offensive players are positioned well behind the line of scrimmage, thus, suggesting a low probability of any present formation. However, at a second time, t0 (e.g., game clock: 12:01, play clock: 13 seconds, universal clock: 16:09:55), certain of the tracked players (e.g., offensive linemen and receivers) appear to have positioned themselves proximate the line of scrimmage, thus, suggesting a higher probability of a pro set offensive formation. At a third time, t1 (e.g., game clock: 11:55, play clock: 07 seconds, universal clock: 16:10:01), certain tracked players (e.g., the receivers and the quarterback) move away from the line of scrimmage, thus, suggesting that a play has begun. Additional times t2 through t5 may be similarly tracked as shown and used by the various engines to hypothesize the occurrence of particular events (formations, play start/stop, penalties, etc.). The play start and end times determined by the play engine 318 may be used to determine the time period for which the location data is utilized for each play event. The tag location data recorded at times t−1 through t5 may provide for a data stream indicating the motions/paths of the various players throughout the duration of a play period. It is noted that FIG. 5 does not illustrate tracking of all the players after t0, or the defensive team players, in order to simplify the illustration. Further, Audio data may be associated with location data. For example, at t−1 the audio data may be players talking, formation callouts, or the like indicating that a play is forming. At t2, the audio data may be an official whistle, quarterback cadence, snap or the like indicating a play has begun. At t−2 through t3 the audio data may include shouting, impact noises, or the like indicating a play is in progress. At t5, the play noise may include an official whistle, a drop in impact noise, or the like indicating a play has ended.

The team formation engine 312 and/or play engine 318 may analyze player dynamics of multiple players, both offensive and defensive, simultaneously in hypothesizing the possible formations, plays, etc. For example, as discussed briefly above, the formation engine 312 and/or play engine 318 may apply different weights to the tag/sensor/location data received for each player based in part on the player's role versus the formation models or play models, as all the individual player dynamics may not fully correlate to a particular formation or play. The formation engine 312 and/or play engine 318 may then analyze the different models and choose the model, or set of models, that have the highest probability of being accurate based on the weights of all the combined inputs.

Example Process or Method Embodiments

FIG. 6 illustrates a flowchart of an exemplary process for determining an event based on audio data and/or location data in accordance with some embodiments of the present invention. The process may start at 702, where a tag ID/filter (e.g. tag ID/filter 304 as shown in FIG. 4) may correlate one or more tags (e.g., tags 102 as shown in FIG. 1) to a participant (e.g., a player, official, ball, etc.) based on a tag-individual correlator. Additionally, in some embodiments, one or more sensors (e.g., sensors 203 as shown in FIG. 2A-C) may be correlated to a participant at 504 based on a sensor—individual correlator. The tags 102 and sensors 203 may be attached to participants, such as to players, officials, balls, field markers, penalty flags, other game equipment, and reference markers on a field of play (e.g., boundary defining reference markers). For example, in the case of players or officials, the tags and/or sensors may be attached to equipment, uniforms, etc., worn or carried by the players or officials.

At 704, the tag ID/filter 304 may correlate one or more audio sensors (e.g., audio sensors 105 as shown in FIG. 1 or sensors 203 as shown in FIG. 2) correlated with a participant or field location based on a sensor-individual correlator. For illustration purposes, FIG. 7 depicts audio sensor 105 separately from sensor 203; however, as discussed above, audio sensor 105 is simply one type of sensor 203.

At 706, blink data may be received from the one or more tags 102 by the receivers (e.g. receivers 106 as shown in FIG. 1). Additionally at 708, in some embodiments, other tag derived data and sensor derived data, such as audio data from sensors 203 associated with the participant, may be received with the blink data. Audio data may also be received separately from the tag blink data by receivers 106.

In another embodiment the audio data and tag location data may be received from a historical database (e.g. historical database 336) or other memory, or from the locate engine (e.g. locate engine 302 as shown in FIG. 4).

At 710, the event engine (e.g. event engine 322 as shown in FIG. 4), or the play engine (e.g. play engine 318 as shown in FIG. 4) may compare audio data to audio profiles. Audio profiles may be comprised of single sounds, such as, an official whistle, impact noise, official call, cheer, scream, yell, or the like; or compilation of sounds such as 1) official whistle, 2) quarterback cadence, 3) snap, 4) impact noise, 5) official whistle. The audio data may be required to be from specified audio sensor 105 (e.g., official whistle) or any available audio sensor. For audio profiles that require a compilation of sounds the sounds may be in a required order, a partially required order, or unspecified.

At 712, the event engine 322 or play engine 318 may determine an event probability for each audio profile. The compared audio profiles are assigned a probability value based on the correlation of the audio data to the audio profile. In an instance in which the event may be determined based on audio data alone the process may continue at 728. If the event requires both audio and location data for determination the process may continue 714.

At 714, tag location data may be determined by the locate engine 302 from the blink data as discussed in FIG. 1-4.

At 716, the play engine 318 or the event engine 322 may compare tag location data to event models. For example an event model may require players assembling on a line of scrimmage, indicating a play forming, players or at least key player roles (e.g. quarterback, linemen, or the like) to stop or pause for a period indicating a play start, rapid movement of players toward and across the line of scrimmage indicating a play in progress, and a secession of motion of players and/or the object ball indicating an end of a play or event.

At 718 the event engine 322 or play engine 318 may determine an event probability based on the correlation of the location data to the event model. The event engine 322 or play engine may assign a probability to the play model(s). In an instance in which the event may be determined by location data probability alone the process may continue at 728.

At 720, time data may be associated with the location data. The locate engine 302 may associate a time or time stamp with the receipt of blink data which may be correlated to the location data. In another embodiment, time data (e.g. universal clock 385 and game clock 380 shown in FIG. 4) is associated with or time stamps the location data by the event engine 322.

At 722, time data may be associated with the audio data. The locate engine 302 may associate a time or time stamp with the receipt of the blink data which may be correlated to the audio data. In another embodiment, time data (e.g., universal clock 385 and game clock 380 shown in FIG. 4) is associated with or time stamps the audio data by the event engine 322.

At 724, the event engine 322 may synchronize location data and audio data by correlating the universal clock 385, game clock 380, or locate engine time stamps. The event engine 322 may perform a synchronization cross check with time data associated by the locate engine 304 to increase accuracy.

At 725, event engine 322 or the play engine 318 may determine an event probability based on audio data and location data. The event engine 322 or play engine 318 may compare the audio data and location data to an event model which correlates to an audio profile. The event engine 322 or play engine 318 may assign a probability value to the event model based on the correlation of audio and location data to the event model. For example, the play engine 318 may determine in an instance in which the players move toward the line of scrimmage in conjunction with play calls and player talking. The play engine 318 may determine in an instance in which it is most likely that a pre-snap formation at the line of scrimmage has occurred (e.g., an offensive team has aligned in a “pro set” formation and a defensive team has aligned in a “3-4” formation) indicating a play is about to begin in conjunction with an official whistle and a quarterback cadence. The play engine 318 may thereafter determine that the offensive and defensive players have begun rapidly accelerating towards and across a line of scrimmage in conjunction with an official whistle and quarterback cadence thereby indicating that a play has begun. The play engine 318 may further determine that an offensive player has been tackled by a defensive player in conjunction with impact noise and an official whistle thereby indicating that a play has concluded.

In another embodiment the event engine 322 or the play engine 318 averages the event probabilities of the audio profiles and event models. The averaging of probability values may be weighted to give a more value to location or audio data. For example the location data may be weighted at 7 and the audio data may be weighted as 3 resulting in location being dominate in the probability and therefore being dominate in the event determination.

At 726, the event engine 322 or the play engine 318 may analyze event probabilities based on audio data and/or location data. The event engine 322 and play engine 318 may compare the probability values assigned to event models and audio profiles to predetermined threshold values. In some embodiments the predetermined threshold values may be applicable to all event models. In other embodiments, the predetermined thresholds may be assigned based on each individual event model or event model type. For example, official calls, plays, formations, or the like may have a higher threshold value than profiles indicative of an injury. For example, an injury event may be determined by a 75 percent probability of audio data containing a scream may satisfy the predetermined threshold. In another example the audio data may be a 80 percent probability of containing an official whistle, a quarterback cadence, a snap, impact noise, and an official whistle; and the location data may contain participants lining up at the line of scrimmage, a pause in motion of specified players, (e.g. quarterback, linemen, or the like, rapid movement of the object ball and participant players, and a secession of motion of the object ball may be required to satisfy the predetermined threshold.

At 728, the event engine 318 and the play engine 322 may determine an event based on event probabilities. In an instance in which the event engine 322 or the play engine 322 determine that an event profile has satisfied a predetermined value an event is generated. An event may comprise, without limitation, an official call, a play, a formation, a touchdown, a field goal, an injury, a change of possession, weather conditions, field position change, downs, or the like. In an instance in which an event is not determined the process may continue at 706 or 708.

At 730, the event, location data, and/or audio data may be output to a memory. Memory may include, but not limited to, dynamic models database 310, formation models database 316, play models database 320, play event audio profiles database 320, official models database 328, historical database 336, or the like.

At 732, the event may be output to one or more user interfaces. User interfaces may include but not limited to, desktop computers, laptop computers, personal data assistants (PDAs), tablet computers, electronic readers, pagers, mobile phone, smart phones, or the like.

At 734, the event may be output to subsystems. Subsystems may include without limitation, a visualization system 340, a game operations system 342, a camera control system 344, a team analytics system 346, a league analytics system 348, a statistics system 350, an XML feed and/or instant message feed 352, a historical data store/engine 336, or other systems as may be apparent to one of ordinary skill in the art in view of this disclosure.

Example Processing Apparatus

FIG. 7 shows a block diagram of components that may be included in an apparatus that may determine events in accordance with embodiments discussed herein. Apparatus 1200 may comprise one or more processors, such as processor 1202, one or more memories, such as memory 1204, communication circuitry 1206, and user interface 1208. Processor 1202 can be, for example, a microprocessor that is configured to execute software instructions and/or other types of code portions for carrying out defined steps, some of which are discussed herein. Processor 1202 may communicate internally using data bus, for example, which may be used to convey data, including program instructions, between processor 1202 and memory 1204.

Memory 1204 may include one or more non-transitory storage media such as, for example, volatile and/or non-volatile memory that may be either fixed or removable. Memory 1204 may be configured to store information, data, applications, instructions or the like for enabling apparatus 1200 to carry out various functions in accordance with example embodiments of the present invention. For example, the memory could be configured to buffer input data for processing by processor 1202. Additionally or alternatively, the memory could be configured to store instructions for execution by processor 1202. Memory 1204 can be considered primary memory and be included in, for example, RAM or other forms of volatile storage which retain its contents only during operation, and/or memory 1204 may be included in non-volatile storage, such as ROM, EPROM, EEPROM, FLASH, or other types of storage that retain the memory contents independent of the power state of the apparatus 1200. Memory 1204 could also be included in a secondary storage device, such as external disk storage, that stores large amounts of data. In some embodiments, the disk storage may communicate with processor 1202 using an input/output component via a data bus or other routing component. The secondary memory may include a hard disk, compact disk, DVD, memory card, or any other type of mass storage type known to those skilled in the art.

In some embodiments, processor 1202 may be configured to communicate with external communication networks and devices using communications circuitry 1206, and may use a variety of interfaces such as data communication oriented protocols, including X.25, ISDN, DSL, among others. Communications circuitry 1206 may also incorporate a modem for interfacing and communicating with a standard telephone line, an Ethernet interface, cable system, and/or any other type of communications system. Additionally, processor 1202 may communicate via a wireless interface that is operatively connected to communications circuitry 1206 for communicating wirelessly with other devices, using for example, one of the IEEE 802.11 protocols, 802.15 protocol (including Bluetooth, Zigbee, and others), a cellular protocol (Advanced Mobile Phone Service or “AMPS”), Personal Communication Services (PCS), or a standard 3G wireless telecommunications protocol, such as CDMA2000 1x EV-DO, GPRS, W-CDMA, LTE, and/or any other protocol.

The apparatus 1200 may include a user interface 1208 that may, in turn, be in communication with the processor 1202 to provide output to the user and to receive input. For example, the user interface may include a display and, in some embodiments, may also include a keyboard, a mouse, a joystick, a touch screen, touch areas, soft keys, a microphone, a speaker, or other input/output mechanisms. The processor may comprise user interface circuitry configured to control at least some functions of one or more user interface elements such as a display and, in some embodiments, a speaker, ringer, microphone and/or the like. The processor and/or user interface circuitry comprising the processor may be configured to control one or more functions of one or more user interface elements through computer program instructions (e.g., software and/or firmware) stored on a memory accessible to the processor (e.g., memory 1204, and/or the like).

In some embodiments, certain ones of the operations above may be modified or further amplified as described below. Moreover, in some embodiments additional optional operations may also be included. It should be appreciated that each of the modifications, optional additions or amplifications below may be included with the operations above either alone or in combination with any others among the features described herein.

Many modifications and other embodiments of the inventions set forth herein will come to mind to one skilled in the art to which these inventions pertain having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the inventions are not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of the appended claims. Moreover, although the foregoing descriptions and the associated drawings describe example embodiments in the context of certain example combinations of elements and/or functions, it should be appreciated that different combinations of elements and/or functions may be provided by alternative embodiments without departing from the scope of the appended claims. In this regard, for example, different combinations of elements and/or functions than those explicitly described above are also contemplated as may be set forth in some of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation. 

That which is claimed:
 1. A method comprising: receiving audio data, wherein the audio data is received from at least one of a memory or a sensor; determining an event probability based on comparing the audio data to an audio profile; and generating an event based on the event probability satisfying a predetermined threshold.
 2. The method of claim 1 further comprising; receiving a tag location data; and determining an event probability based on comparing the tag location data to an event model.
 3. The method of claim 2 further comprising: associating a time data with the audio data; and associating the time data with the location data.
 4. The method of claim 4 further comprising: synchronizing the audio data and location data based on the time data.
 5. The method of claim 2 further comprising: determining an event probability based on comparing the audio data and location data to an event model.
 6. The method of claim 1 further comprising: causing the event to be stored in a memory.
 7. The method of claim 1 further comprising: causing the event to be displayed on a user interface.
 8. The method of claim 1 further comprising; outputting the event to at least one of the group visualization system, a game operations system, a camera control system, a team analytics system, a league analytics system, a statistics system, an XML feed and/or instant message feed, and a historical data store/engine.
 9. An apparatus for determining play events comprising at least one processor and at least one memory including computer instructions configured to, in cooperation with the at least one processor, cause the apparatus to: receive audio data, wherein the audio data is received from at least one of a memory or a sensor; determine an event probability based on comparing the audio data to an audio profile; and generate an event based on event probability satisfying a predetermined threshold.
 10. The apparatus of claim 8 further comprising the at least one memory and the computer program instructions configured to, in cooperation with the at least one processor, cause the apparatus to: receive a tag location data; and determine an event probability based on comparing the tag location data to an event profile.
 11. The apparatus of claim 9 further comprising the at least one memory and the computer program instructions configured to, in cooperation with the at least one processor, cause the apparatus to: associate a time data with the audio data; and associate the time data with the location data.
 12. The apparatus of claim 10 further comprising the at least one memory and the computer program instructions configured to, in cooperation with the at least one processor, cause the apparatus to: synchronize the audio data and location data based on the time data.
 13. The apparatus of claim 9 further comprising the at least one memory and the computer program instructions configured to, in cooperation with the at least one processor, cause the apparatus to: determine an event probability based on comparing audio data and location data to an event model.
 14. The apparatus of claim 8 further comprising the at least one memory and the computer program instructions configured to, in cooperation with the at least one processor, cause the apparatus to: cause the event to be stored in a memory.
 15. The apparatus of claim 8 further comprising the at least one memory and the computer program instructions configured to, in cooperation with the at least one processor, cause the apparatus to: cause the event to be displayed on a user interface.
 16. The apparatus of claim 8 further comprising the at least one memory and the computer program instructions configured to, in cooperation with the at least one processor, cause the apparatus to: output the event to at least one of the group visualization system, a game operations system, a camera control system, a team analytics system, a league analytics system, a statistics system, an XML feed and/or instant message feed, and a historical data store/engine.
 17. A computer program product for monitoring participants, the computer program product comprising a non-transitory computer readable storage medium and computer program instructions stored therein, the computer program instructions comprising program instructions at least configured to: receive audio data, wherein the audio data is received from at least one of a memory or a sensor; determine an event probability based on comparing the audio data to an audio profile; and generate an event based on event probability satisfying a predetermined threshold.
 18. The computer program product of claim 15 further comprising computer program instructions at least configured to: receive a tag location data; and determine an event probability based on comparing the tag location data to an event profile.
 19. The computer program product of claim 16 further comprising computer program instructions at least configured to: associate a time data with the audio data; and associate the time data with the location data.
 20. The computer program product of claim 17 further comprising computer program instructions at least configured to: synchronize the audio data and location data based on the time data.
 21. The computer program product of claim 16 further comprising computer program instructions at least configured to: determine an event probability based on comparing audio data and location data to an event model.
 22. The computer program product of claim 15 further comprising computer program instructions at least configured to: cause the event to be stored in a memory.
 23. The computer program product of claim 15 further comprising computer program instructions at least configured to: cause the event to be displayed on a user interface.
 24. The computer program product of claim 15 further comprising computer program instructions at least configured to: output the event to at least one of the group visualization system, a game operations system, a camera control system, a team analytics system, a league analytics system, a statistics system, an XML feed and/or instant message feed, and a historical data store/engine. 